Timeline for Blind upvoting of posts on Code Review
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:09 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jun 28, 2014 at 0:24 | comment | added | cimmanon | @Mat'sMug I'm more forgiving about CSS validation issues since invalid CSS tends to either not work (and its obvious that it doesn't work) or they're using browser specific styles (eg. filter for gradients in IE8). Invalid HTML is another thing entirely and can cause unexpected problems when the browser tries to compensate for them, which in turn causes the author to overcompensate (eg. paragraph within a paragraph will render as paragraph following a paragraph, which may cause the author to reduce the margins on paragraphs). | |
| Jun 27, 2014 at 23:18 | comment | added | Simon Forsberg | @cimmanon I think the most common reasons for why people have not run the code through linters is because they're either too lazy or just simply not aware of them. It's up to reviewers to educate them in this aspect. | |
| Jun 27, 2014 at 23:17 | comment | added | Simon Forsberg | @Mat'sMug Just because it doesn't live up to the standard doesn't always mean that it's not working. Some might be closed for it, but today's browsers and applications are often too good at fixing the brokenness for it to be considered as truly broken. | |
| Jun 27, 2014 at 22:53 | comment | added | Mathieu Guindon | @cimmanon that's a pretty interesting point you bring up here, ..do non-validating CSS questions gather close votes? I think they would belong with non-working code questions... | |
| Jun 27, 2014 at 20:39 | comment | added | cimmanon | Basic things like running your code through linters (hlint for Haskell) could easily fall under "research effort" for CR. I follow the CSS tag myself and see far too many questions that have markup that doesn't validate. Or check out this question where the author clearly didn't bother to research what it means to be responsive because there's no media queries involved. | |
| Jun 27, 2014 at 17:39 | history | answered | Simon Forsberg | CC BY-SA 3.0 |