- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Sat, 25 Jun 2016 23:23:03 +0000
- To: public-css-archive@w3.org
The only instance of a webkit property name (outside of examples) I see is user-select in the ED of UI-4, and that was only added less than two months ago. Given the number of webkit prefixes in the compat spec, I think the consistency argument favors keeping them out of CSS specs, and I'll argue that one should be removed as well (and added back to the compat spec). I understand the unfortunate platform dependency, and agree that those prefixed items that have become problematical in the wild should be documented and standardized for web compatibility, but that's what the compat spec is for (modularity FTW). Yes, we have to live with them (for now at least), but we don't want to spread the disease. The last thing we want to do is encourage authors to use them (both of the authors that actually read our specs), or give any kind of signal that someone implementing a CSS engine that doesn't necessarily care about web compat (like, say an ePub reader or offline formatting engine) should implement these things. What's next, adding conformance tests for -webkit- properties? -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/237#issuecomment-228575529 using your GitHub account
Received on Saturday, 25 June 2016 23:23:05 UTC