Re: [csswg-drafts] [css-cascade][CSSOM] Protected properties (#13470)

I deliberately phrased this as a question because I’m not sure it would really be helpful or useful in practice – and outweigh the costs of implementation and of potentially maintaining legacy aliases in the future. 

For authors, all of this would only matter if they could act on the values of those properties, i.e. through the OM in scripts or with `@supports`, `if()` etc. in CSS. Some of them would closely map to selectors, so write-protection essentially avoids circular dependencies / contradictions as in hypothetical `:link {content-link: none}`.

In theory, browsers could expose those pseudo-internal properties from the second use case in special stylesheets to implement arbitrary document languages or at least XML dialects. This would probably require some other changes and allen's as well, though, e.g. URLs in `attr()`.

-- 
GitHub Notification of comment by Crissov
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13470#issuecomment-3877565798 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 10 February 2026 13:21:19 UTC