> Quick question: how many of these have you actively used in production?
> Container Queries
I haven't used this, but it looks super useful.
> Style Queries
Eh, I'm sure this is useful for situations that don't come up very often.
> CSS Layers
Ugh, I'm not going to use this overly-complex silliness, and I'm not looking forward to debugging this when other people use this.
> Subgrid
Again, overly complex. Grid could already do everything this can do, more simply.
> Native Selector Nesting
I'm already using this.
> Anchor Positioning
Eh, I already had solutions to this problem, but this seems like it probably communicates intent a bit better. I guess I'll pick that up.
> :has, :is, :where
:has is useful
:is... okay, fine, syntactic sugar.
:where I don't believe in hell. If I did, I'd be against it because burning someone for eternity is inhumane. But I might be willing to make an exception for people who write CSS that requires you to read the MDN article on Specificity to understand it.
> Logical Properties
Perhaps useful for situations that don't come up very often. Seems complex, but that might be because the thing it's representing is inherently complex.
> Scroll-Linked Animations
Okay, someone who isn't me will probably do really cool things with this.
> View Transitions
Another thing that seems complex, but possibly because the thing it's representing is inherently complex.
There isn't a great way to make the <li> adhere to the grid template areas, because without subgrids only direct children (the ul) have coordinate attributes.
I think subgrid might give you a freer hand. Because if I remember correctly, the trouble with display:contents is that no other styles you put on that element will affect elements within it. This means shifting all styles down a node, which can be a real pain and have knock-on effects.
`display: contents` has a11y concerns in a lot of scenarios. The `ul` will be hidden from a screenreader and it will be read as `h1, li, li, li...` etc.
After having seen a11y written about 100x times in Svelte warnings, it's finally dawned on me that it means accessibility, which is somewhat ironic that I had no idea what it meant all those times before.
Please don't take this the wrong way, but can I ask how you personally find answers to similar solutions when they come up in your work/personal life?
The first thing I do when I see an acronym or word I don't understand is go to Google and type `what is a11y webdev` or whatever. I think you get the idea.
This has been a part of my life for almost 2 decades now so I'm curious how others handle the situation! What made you wait so long to find the answer? Did you eventually search for it, or did you finally read some document that spelled it out explicitly?
Again, genuinely curious! I assume many people operate like I do and there is a line between explaining too little and too much. Understanding how others approach these problems hopefully will help me improve my own communication in the long run.
I would normally do something similar. The context in which I was seeing these warnings was that I was working on a new UI for a VST plugin using web front-end tech, something novel for me so I was more interested in getting it to work before dealing with what the warnings meant.
It was the parent comment mentioning a11y and screen-reader in conjunction that made me make the connection, I just found it hilarious that the term a11y itself is so inaccessible if you don't already know what it means!
Full stack. Typically Django+React, using React as a component library not an SPA framework. But I've worked on stacks that deviate from that pretty significantly in the not-too-distant past.
> Container Queries
I haven't used this, but it looks super useful.
> Style Queries
Eh, I'm sure this is useful for situations that don't come up very often.
> CSS Layers
Ugh, I'm not going to use this overly-complex silliness, and I'm not looking forward to debugging this when other people use this.
> Subgrid
Again, overly complex. Grid could already do everything this can do, more simply.
> Native Selector Nesting
I'm already using this.
> Anchor Positioning
Eh, I already had solutions to this problem, but this seems like it probably communicates intent a bit better. I guess I'll pick that up.
> :has, :is, :where
:has is useful
:is... okay, fine, syntactic sugar.
:where I don't believe in hell. If I did, I'd be against it because burning someone for eternity is inhumane. But I might be willing to make an exception for people who write CSS that requires you to read the MDN article on Specificity to understand it.
> Logical Properties
Perhaps useful for situations that don't come up very often. Seems complex, but that might be because the thing it's representing is inherently complex.
> Scroll-Linked Animations
Okay, someone who isn't me will probably do really cool things with this.
> View Transitions
Another thing that seems complex, but possibly because the thing it's representing is inherently complex.