- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 05:34:36 +0000
- To: public-css-archive@w3.org
> is exploring a bunch of difficulties with globally-unique names, and I suspect they hold almost as much for CSS-assigned names as much as they do for IDs. They don't, because our features that name elements generally aren't "global". Anchor names and timeline names can both be scoped, for instance, so you can reuse the same name multiple times across a page; in particular, you can apply the same name to every instance of a component, and scope it to that component. We just had a discussion yesterday about a new name-defining feature (animation triggers) and resolved to align it with that practice too, so that name will be scoped in the same way. (Occasionally someone will have a use-case where the global nature of other names, like animations, might be annoying, but they've always been relatively niche use-cases, and usually involve either a preprocessor or JS anyway so it's not a huge deal.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12590#issuecomment-3209061089 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 05:34:37 UTC