- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Oct 2017 23:13:38 +0000
- To: public-css-archive@w3.org
This isn't going to happen, and fairly intentionally - if we kept around invalid/unrecognized stuff and made it easy for JS to fill in the functionality, then it would be really easy for pages to "squat" on names, making it harder for us to change or add new CSS in the future. This sort of thing is an occasional problem in JS already. Instead, CSS is growing more robust custom-whatever functionality in the Houdini WG; custom properties are the start, and we'll move toward custom functions, custom at-rules, and others in the future. These all live in a different namespace (due to the `--` prefix) which normal CSS will never use, so it's safe to use whatever names you want there. As Florian said, we will be adding an explicit parser API that lets you re-use the general CSS syntax for other things, and that *will* let you manually reparse a stylesheet's text and see what all is in there without having "invalid" things thrown away, but it's a sufficient barrier to usage that it probably won't harm CSS's future evolution in the way I described above. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1858#issuecomment-335974702 using your GitHub account
Received on Wednesday, 11 October 2017 23:13:43 UTC