- From: Mike Bremford via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Mar 2021 08:53:52 +0000
- To: public-css-archive@w3.org
What we have now is a fairly simple naming scheme - no hyphen = universal and specified in CSS, one hyphen = browser-wide, browser-specific and possibly experimental, two-hyphens = site-specific, variable, and under author control. First, there's a lot to be said for looking at a property and immediately knowing its provenance. I'm not sure authors would give that up if they thought about it. Second, if single-hyphen prefixes were used universally, you immediately introduce a whole new class of failure: authors choosing a prefix, unaware that it's in use by a CSS engine they haven't heard of. Try and render that page on that engine and you'll potentially get different results. I'm sure you'd steer clear of `-moz-NNN`, `-webkit-NNN` or `-chrome-NNN`, but off the top of my head I can name six other prefixes in use today, and I'm sure there are more. In short, from an author perspective you're saving a hyphen. From a vendor perspective outside of the big-three, what you're suggesting is a long-term disaster. -- GitHub Notification of comment by faceless2 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6099#issuecomment-800076066 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 08:53:54 UTC