- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Oct 2024 13:47:03 +0000
- To: public-css-archive@w3.org
My point is that it isn't doing the right thing, it's obfuscating doing an unreliable thing. If I want the thing to work for both SPA and MPA, then I'll use `attr(id ident)`, because `attr(id ident, match-element)` doesn't work MPA. The fact that it 'tries' to work and ends up working partially is confusing. If I only want the thing to work SPA, then `match-element` is fine, and means I don't have to assign IDs everywhere, and it works nicely with pseudo-elements. I guess it's nice that `attr(id ident, match-element)` is possible, but I don't when I'd ever want that. I want the thing that works for SPA and MPA (and requires `id`s everywhere), _or_ I'm ok with the SPA-only thing. The most important thing is that I want it to be clear which I'm picking. If I'm intending for it to work for SPA and MPA, I'd much rather it fails in both cases if I've forgotten an `id`. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2449884499 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 31 October 2024 13:47:04 UTC