I’ve been hoping that we’d have enough support for queries based on an element’s parent that we could do bottom-up element/container queries and never have to think about specific screen sizes ever again
]]>For text stroke, you should be able to use it on non-SVG elements already but prefixed (example lifted from CSS-Tricks!) — paint-order also works here:
-webkit-text-stroke-width: 1px;
-webkit-text-stroke-color: black;
So I guess this falls back to your unprefix all the things section. (though I don’t know if there’s a well-defined spec yet)
I’d love exclusions, not that I have a lot of use cases for them, but still love the idea. And I feel the same about masonry, hoping a consensus can be reached.
As far as grid rules, I like that a lot. Makes me think of the :nth-child(n) syntax, could even look like :nth-rule(2 of row) maybe? (perhaps too complex for such a simple feature, and perhaps a confusing name)
Finally, I already use custom media queries and transform them with LightningCSS for my site’s build, so I’d love to see those make it to browsers. I hope we can also use them in container queries.
]]>