5 ms·
> As a whole, modern CSS features feel unintuitive and often require a historical knowledge of the problems this new feature X was trying to solve There's no r
by Frotag 4y ago
> As a whole, modern CSS features feel unintuitive and often require a historical knowledge of the problems this new feature X was trying to solve
There's no real way to debug unexpected behavior short of digging through the W3 spec. For example you can't set height / width on inline elements, but you'll never see any error messages or warnings in devtools / IDEs when you try. It doesn't help that tutorials rarely discuss how "layout algorithms" [0] (block, inline, flex, grid) affect certain rules.
[0] - https://www.joshwcomeau.com/css/understanding-layout-algorithms/ https://www.joshwcomeau.com/css/understanding-layout-algorit...
- alwillis 4y agoyou'll never see any error messages or warnings in devtools / IDEs when you try. I’ve seem dev tools highlight code that either doesn’t make sense or doesn’t have any affect. I wonder if something like Stylelint [1] would catch this. [1]: https://stylelint.io https://stylelint.io