That so much of the 2003 draft of the Generated and Replaced Content spec died without being implemented. There was so much cool stuff in there, especially ::outside(1), ::outside(2) etc. which would have helped considerably in avoiding having to create wrapper divs to produce a whole range of effects. ::inside(n) would be so useful too.
Absence of SASS style mixins, which would allow for declaration-sets to be combined and re-used.
The responsiveness of tables is problematic, for sure. But I don't think CSS can be blamed for that. It is inherent in what a table is, and the necessity of that organisation of the data for correct accessibility that means that there will always be limitations to the flexibility of their presentation.
That so much of the 2003 draft of the Generated and Replaced Content spec died without being implemented. There was so much cool stuff in there, especially ::outside(1), ::outside(2) etc. which would have helped considerably in avoiding having to create wrapper divs to produce a whole range of effects. ::inside(n) would be so useful too.
Absence of SASS style mixins, which would allow for declaration-sets to be combined and re-used.
I hate tables so much! I prefer to create divs instead of tables! I just ... can't use them. Can't make them responsive enough!
The responsiveness of tables is problematic, for sure. But I don't think CSS can be blamed for that. It is inherent in what a table is, and the necessity of that organisation of the data for correct accessibility that means that there will always be limitations to the flexibility of their presentation.
True, CSS is not guilty. But it's not helping with managing them either :(