CSS WG Blog Minutes San Diego F2F August 2012: Experim…

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

Shipping

• 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.

Prefixing

• 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.

Full minutes

« Previous article Next article »

Comments

• Google verlaat WebKit en zal nu Blink engine gebruiken in Chrome 2013-04-04 20:41:48 [...] Blink is in meer detail uitgelegd op de Blink’s Chromium Project pagina. Daar staat onder meer dit te lezen over vendor prefixen: Historically, browsers have relied on vendor prefixes (e.g., -webkit-feature) to ship experimental features to web developers. This approach can be harmful to compatibility because web content comes to rely upon these vendor-prefixed names. Going forward, instead of enabling a feature by default with a vendor prefix, we will instead keep the (unprefixed) feature behind the “enable experimental web platform features” flag in about:flags until the feature is ready to be enabled by default. Mozilla has already embarked on a similar policy and the W3C CSS WG formed a rough consensus around a complementary policy. [...]
• Revista Espírito Livre » Blog Archive » Google Blink faz fork do WebKit 2013-04-06 16:34:22 [...] O Google aponta que a Mozilla está se movendo em direção a uma política semelhante e que o W3C também tem explorado uma ideia [...]
• Google Officially Forking Webkit to be Google Blink | emka.web.id 2013-04-09 05:13:32 [...] Among other changes Google will be making, it is moving to a “no prefix” model of web enhancements. Vendor prefixes have been used in browsers to denote experimental features for many years. Unfortunately, web developers have often used, and relied on, those prefixes. With Blink there will be no prefixes except those inherited from WebKit. Instead, developers will have to turn on experimental features on an about:flags page until the feature is suitable to be enabled by default. Google points out that Mozilla is moving towards a similar policy and that the W3C is exploring a similar idea. [...]
• Vendor Prefixes: Blink, and you’ll miss them.|Shoutleaf 2013-05-16 00:11:58 [...] This is where all the vendors are headed, and the W3C working group on CSS has already put together a policy that rang the death knoll of vendor prefixes. PermalinkComments RSSComments are closed, but you [...]
• Paul Irish on Chrome Moving to Blink | iMakeInternet.com 2013-06-16 17:34:26 [...] They’re great in theory but turns out they fail in practice, so we’re joining Mozilla and the W3C CSS WG and moving away them. There’s a few parts [...]
• » Vendor Prefixes: Blink, and You’ll Miss Them 2013-10-25 23:49:44 […] This is where all the vendors are headed, and the W3C working group on CSS has already put together a policy that rang the death knoll of vendor prefixes. This article is cross-posted: it originally appeared […]
• Why are there vendor prefixes in CSS3? - HTML5 Solutions - Developers Q & A 2013-11-16 02:49:07 […] Originally prefixes went away once a module and its implementations were finalized (CSS3 itself is never finalized because it’s always growing). These days, measures are being taken to eliminate the use of prefixes for developing technologies almost entirely; see Chromium/Blink and this CSSWG blog post. […]