Changes between Version 14 and Version 15 of DeprecatingFeatures
- Timestamp:
- Oct 2, 2012 10:15:26 AM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DeprecatingFeatures
v14 v15 51 51 * ''Clear path forward.'' When we remove a vendor prefix, web developers have a clear path forward: use the unprefixed version of the API. This clear path forward means that we won't strand developers when we remove a vendor-prefixed version of an API. 52 52 53 * ''Standards citizenship.'' Many W3C working groups, including the CSS working group, [http://wiki.csswg.org/spec/vendor-prefixes requestthat implementors remove support for vendor prefixed features] once the specifications of the features reach a certain level of maturity, typically Candidate Recommendation. To be good citizens of these standards bodies, we should make an effort to remove vendor prefixes, even if doing so would incur a larger compatibility cost than we would otherwise prefer.53 * ''Standards citizenship.'' The CSS Working Group [http://wiki.csswg.org/spec/vendor-prefixes is considering requesting that implementors remove support for vendor prefixed features] once the specifications of the features reach a certain level of maturity, typically Candidate Recommendation. To be good citizens of these standards bodies, we should make an effort to remove vendor prefixes, even if doing so would incur a larger compatibility cost than we would otherwise prefer.