Canmove, confirm
2,672
edits
Changes
Very UNLIKELY that we're going to support webkit prefixes. Turned this corner a while ago and we should make this clear now so we indicate our current (better) position.
= CSS vendor-prefix compatibility =
'''Problem: WebKit mobile web monoculture.''' There is currently (still) a WebKit mobile web monoculture, numerous sites that have WebKit-specific content and reduced content/style/functionality for everyone else, despite numerous evangelists at Mozilla, Opera, and Microsoft working with web developers to publish standards-based cross-browser content.
'''What is Mozilla doing about the problem?'''
'''Is Firefox going to support WebKit prefixes?'''
* '''Very likely, on properties Mozilla deems necessary according to UNLIKELY''' - per our [https://bugzilla.mozilla.org/show_bug.cgi?id=708406 study of -webkit- dependent sites]and experiments with some -webkit- prefix support see if it fixes sites (answer: very few, and even breaks some).
'''If so, when is that happening?'''
* We don't have a specific release or date yet. We are continuing to study which sites appear to require Webkit-prefixed properties, and if implementing them actually fixes those sites or not (WebKit-specific sites sometimes depend on other WebKit-specific features, e.g.: touch events, WebSQL, etc.)
For more details, read on, and see also * [http://www.alistapart.com/articles/the-vendor-prefix-predicament-alas-eric-meyer-interviews-tantek-celik/ A List Apart: The Vendor Prefix Predicament]* [https://groups.google.com/forum/?fromgroups=#!msg/mozilla.dev.platform/itl6mtx2dxI/mbdPvbexB2EJ Policy for experimental CSS features in Gecko]
__TOC__
* Prioritize [[standards]] for commonly used -webkit- prefixed properties.
** [[CSS/text-size-adjust|text-size-adjust]]
** [[CSS3]] Animations(Mozilla ships unprefixed support)** CSS3 Transitions(Mozilla ships unprefixed support)** CSS3 Transforms(Mozilla ships unprefixed support)
* Consider implementing some -webkit- prefixed properties.
** Experiment with implementation and see if that fixes sites (the efficacy test).
*** So far, efficacy is poor (very few sites are fixed), and there are negative side-effects (some sites got ''worse'' with -webkit- prefixes).
== straw proposal downsides ==
== possible downside mitigation ==
* In the short term we can at least remove pain for web authors and users.
* In the long term we can ensure the unprefixed properties (in CR drafts) work and encourage authors to switch to them.Done for:* * transforms** transitions** animations** border-image See and try <cite>[http://dbaron..org/log/20130225-removing-prefixes How you can help with removing -moz- prefixes]</cite>.
== questions and methodology ==
** put the energy first into contributing and passing test suites instead.
* ...
See also: [https://groups.google.com/forum/?fromgroups=#!msg/mozilla.dev.platform/itl6mtx2dxI/mbdPvbexB2EJ Policy for experimental CSS features in Gecko].
== meetings minutes discussions ==
* Propose -webkit- properties to implement in Firefox Mobile, each based on specific data from [https://bugzilla.mozilla.org/show_bug.cgi?id=708406 bug 708406].
** -webkit-... due to prevalence of usage in x% of sites ...
* ...(none so far that are justified by the experiments done / data collected)
== Data on vendor-specific prefixes ==
