Timeline for CSS attribute Selector: responsive grid performance
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2015 at 19:18 | vote | accept | superUntitled | ||
| Jan 27, 2015 at 15:25 | vote | accept | superUntitled | ||
| Jan 27, 2015 at 19:18 | |||||
| Jan 27, 2015 at 15:25 | comment | added | superUntitled | Your answer got me thinking about a third way of going about this. I will use use the bootstrap method as mix-in's for the responsive divs. | |
| Jan 27, 2015 at 15:23 | comment | added | superUntitled | Thank you again @cimmanon for re-affirming the necessity of semantics in html. While I do go back and forth on semantic and presentational class names, my main objective in writing code fro the front end is that it is: accessible (ADA compliant), semantic and maintainable. The first is a non-compete value, but there is a balance between the second two. | |
| Jan 27, 2015 at 15:11 | comment | added | superUntitled | Thanks @cimmanon, I totally agree with you (and Brad) on using the design to determine breakpoints (although this too has it's imperfections). 'these breakpoints are hypothetical'. | |
| Jan 27, 2015 at 15:00 | history | answered | cimmanon | CC BY-SA 3.0 |