Post
So I was reading the new #CSS selectors level 5 draft, like one does, and what do I see? `label /for/ input` will let us select the input referenced by a label's for attribute? I don't have a good use case right now, usually `label + input` or `label > input` does the trick, but still… very cool to have the option. Interested to see what other use cases people come up with.
https://www.w3.org/TR/2026/WD-selectors-5-20260217/#combinators
Local link seems interesting as well for anyone adding icons to external sites.
`a:not(:local-link)::after { content: ' ↗️'; }`
And there' a functional notation to match the current subfolder? That's wild. Again, not a lot of use-cases racing through my mind (maybe it could be helpful in a blog sidebar if your permalinks are /yyyy/mm/dd to highlight an archive list for the current month/year), but I still find it very interesting to have the option!
https://www.w3.org/TR/2026/WD-selectors-5-20260217/#local-pseudo
@chriskirknielsen personally I think I'm gonna love that one. Assuming it checks the local domain? My clients often copy the whole link instead of just the bit after their domain...
@netzhexe Yeah that's my understanding, too. That should allow us to remove any `[href^="https://"]:not([href^="https://example.com/"])` and such. Whether the link is `https://example.com/page` or just `/page`, it should match `:local-link` on the `example.com` domain. Unless I completely misread this haha.
@chriskirknielsen
Meh, I think users rarely care or think about links being "internal" or "external."
Even with the complexity of `:local-link(0)`, `:local-link(1)`, etc., it still can't treat `example.com` and `www.example.com` as "internal" but `cwilcox.example.com` as "external."
@netzhexe
@cwilcox808 @chriskirknielsen hmm you have a point 🤔 we shall see how it turns out...
@chriskirknielsen gods that would be so gooooood! I'm telling people over and over and over AGAIN currently 🫠
