Changes between Version 13 and Version 14 of DeprecatingFeatures


Ignore:
Timestamp:
Sep 21, 2012 5:31:39 PM (10 years ago)
Author:
abarth@webkit.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeprecatingFeatures

    v13 v14  
    5151 * ''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.
    5252
    53  * ''Standards citizenship.''  Many W3C working groups, including the CSS working group, [http://wiki.csswg.org/spec/vendor-prefixes request 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 whenever possible, even if doing so would incur a larger compatibility cost than we would otherwise prefer.
     53 * ''Standards citizenship.''  Many W3C working groups, including the CSS working group, [http://wiki.csswg.org/spec/vendor-prefixes request 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.