Explore >> Select a destination
|
You are here 
|
codersblock.com | ||
| | | | |
bryanlrobinson.com
|
|
| | | | | Layout in CSS is hard. We've spent the 2 decades since the inception of CSS battling with its idea of how to lay out content on the web. When we moved from table-based layouts to CSS layouts with floats and positioning, we gained a LOT of flexibility, but we also lost things like vertical centering that tables afforded us. Floats and positioning got us a long way to making really nice looking sites, but with the advent of responsive design and fluid layouts, the struggle has been real... | |
| | | | |
inclusive-components.design
|
|
| | | | | ||
| | | | |
ryanseddon.com
|
|
| | | | | I've seen a lot of commentary on the for, and against of using the CSS property display: table, a lot of it negative. It takes us back to the dark ages, using tables for layout. These people tend to forget that CSS is purely presentational and setting something as display: table is not the same as using the table tag. A screen reader going over a layout styled using the CSS table model will not get confused and muddled up. It will in fact breeze through a layout done correctly no matter which technique used floats or CSS tables. The display properties values: table, table-cell, table-row etc are named due to the fact its presentational result is that best described of how a table would work and the similarities end there. | |
| | | | |
sarasoueidan.com
|
|
| | | - The personal website of Sara Soueidan, inclusive design engineer | ||
