- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Mar 2021 19:56:47 +0000
- To: public-css-archive@w3.org
> Since the one hyphen case is, by definition, irrelevant for public stylesheets That's clearly not true. Vendor-prefixed properties are used on millions, billions of public facing websites. > The potential namespace conflicts exist regardless the number of hyphens in front. In practice, they are highly unlikely even without a registry. The chance of collision _on a single page_ is remote, which is why the current system works. Because your proposal combines the namespace used by authors with the namespace use by each browser vendor, what you need to consider is the chance of collision for _any combination of page and that browser_. As more pages are processed by that engine, that number approaches one. To illustrate: I define `-moz-NNN` custom property in a page, and it happens to collide with an internal undocumented property name used in Firefox. My page now renders differently in Firefox than it does in Webkit, or Firefox crashes because I've messed with some internal state. Multiply four billion webpages by _N_ vendor prefixes, and the likelihood of this happening approaches certainty. It's bad for vendors, bad for authors, and brings virtually no benefit. It's not a good idea. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6099#issuecomment-800561050 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 March 2021 19:56:49 UTC