10 comments

[ 1.8 ms ] story [ 28.2 ms ] thread
Wow container queries eliminate a whole class of dynamic CSS through js/native DOM!

https://www.bram.us/2020/11/05/container-queries-are-coming-...

That being said, if only they added a :on-click pseudoselector the biggest class of JS for CSS would disappear and both performance and clarity would be improved. But it doesn't seems that's ever going to happen

Why not?
Well I can't find a proposal on the web and the idea is sufficiently basic and fundamental to have been considered by the whatwg/w3c therefore they must have dismissed it for unknown reasons. They might reconsider it too so maybe
Well there is no Dom state capturing whether something was clicked or not afaik. Whereas something like focus you can query the Dom for
What is a use case for :on-click...? I can't think of one
:on-click? do you mean :active?
more like state of tailwindcss
(comment deleted)
Wow. HN mostly not giving a shit is an interesting thing to note.
These days when I get burnt by CSS incompatibility or bugs it's Firefox 3/4ths of the time and Safari 1/4th of the time.

Firefox still doesn't support the 7 year old feature backdrop-filter when even Safari does.