- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Mar 2021 18:10:24 +0000
- To: public-css-archive@w3.org
`@namespace` doesn't work that way. It's for referring to XML namespaces, and only works in tagname and attribute selectors. Namespaces are also scoped to the stylesheet they appear in, and don't affect imported or importing sheets, meaning it wouldn't help with this issue in any case, since vendored properties often appear in other stylesheets; we'd have to grandfather in all the existing prefixes and then require any new prefixes to spam `@namespace` rules around. (Which I'm moderately opposed to in any case, since XML namespaces are a terrible design, for several reasons.) Since the use-case here is "it would be nice if we could use one less dash in custom properties", but the presence of two dashes doesn't seem to have meaningfully impaired uptake of custom properties nor spawned any major complaints that I'm aware of, I don't see a reason why we should introduce the potential confusion of mixing vendored prefixes with custom properties, not to mention increasing the complexity of other little-known features just to solve the new problems subsequently introduced by this change. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6099#issuecomment-801300306 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 March 2021 18:10:26 UTC