Minutes San Diego F2F August 2012: Experimental Features Policy
Experimental Features Policy
The CSSWG discussed the various problems being handled currently by the vendor prefixing policy and how to solve them better. A rough consensus was adopted around a variant of dbaron’s proposal, which is summarized from the minutes below. A more formal version will be written up for formal adoption in the near future.
Section A: Non-Web Features
If it’s not Web-ready, and must ship, ship it prefixed and don’t expose to Web. (Prefixes here avoid clashes with future Web features.)
Section B: Standards-track Features
- Experimental features ship only in non-release builds. CR-level features ship in release builds as currently specified.
- Release pre-CR if 3 browsers implement, and we have rough interop, and we agree it’s a good idea.
- If a browser breaks the rules and ships in a release anyway, and we have rough interop and agree it’s a good idea, everyone can release.
- If current criteria are satisfied, ship unprefixed.
- If it’s not stable (i.e. CR + some respectable if incomplete set of passing tests), ship both prefixed and unprefixed versions so that authors can tweak the input to specific implementations.
« Previous article
Next article »