<story><title>What You Need to Know about Modern CSS (Spring 2024 Edition)</title><url>https://frontendmasters.com/blog/what-you-need-to-know-about-modern-css-spring-2024-edition/</url></story><parent_chain></parent_chain><comment><author>exceptione</author><text>Some additions are nice, but I have my doubts about where this is going. As usual, Google throws in tons of extra stuff. To compute the size, position and appearance of anything, engines have to deal with a growing list of instructions, that all brings conflict. We had floats, flex, grids, position, and now anchor positioning as well.&lt;p&gt;It strikes me that the more useful additions are implemented by Firefox, and the lesser ones not.&lt;p&gt;I had expected that by now we would have a super light (kernel) spec for SPAs, and the heavier spec for design heavy documents. Chrome cannot keep up with Firefox wrt CSS performance.
I don&amp;#x27;t understand why Google is overloading its own camel; the web is not going to render faster with more added complexity.</text></comment>
<story><title>What You Need to Know about Modern CSS (Spring 2024 Edition)</title><url>https://frontendmasters.com/blog/what-you-need-to-know-about-modern-css-spring-2024-edition/</url></story><parent_chain></parent_chain><comment><author>doix</author><text>The :has selector is huge if you like customizing sites with grease monkey. You can now modify parents based on their children with pure css. Saves you having to use mutation observers in those cases (assuming the site is built with a React-like thing).</text></comment>