25
edits
Platform/Layout/CSS Compatibility: Difference between revisions
added banner note on history for page
Paul.irish (talk | contribs) (comparison is android chrome, not android browser) |
(added banner note on history for page) |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= CSS vendor-prefix compatibility = | = CSS vendor-prefix compatibility = | ||
<div style="width: 80%; padding: .5em 4em; background-color: #fc0;font-size: 1.rem;margin:auto;"> | |||
This page is preserved to maintain history and not intended for current status of projects. | |||
</div> | |||
'''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?''' | |||
# '''Studying''' the extent of -webkit- property dependence ([https://bugzilla.mozilla.org/show_bug.cgi?id=708406 Bugzilla 708406]). | |||
# '''Prioritizing standardization''' for such properties that have high levels of -webkit- prefix usage on the web ([[CSS/text-size-adjust|text-size-adjust]], [[CSS3]] Animations/Transitions/Transforms). | |||
# '''Experimenting''' with some -webkit- prefix support to see if it fixes sites. | |||
'''Is Firefox going to support WebKit prefixes?''' | |||
* '''Very 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__ | |||
== problem statement == | == problem statement == | ||
| Line 11: | Line 34: | ||
See http://people.mozilla.com/~atrain/mobile/Evangelism/chrome-compare/chrome-compare.html for a comparison of Chrome on Android vs. Mobile Firefox mobile/13.0a1 Nightly | See http://people.mozilla.com/~atrain/mobile/Evangelism/chrome-compare/chrome-compare.html for a comparison of Chrome on Android vs. Mobile Firefox mobile/13.0a1 Nightly | ||
Feel free to add specific problematic sites here so QA & [[Mobile/Evangelism|Evangelism]] can investigate and follow-up: | |||
* ... | * ... | ||
See the [https://bugzilla.mozilla.org/show_bug.cgi?id=739832 tracking bug 739832] for more. | |||
== goals == | == goals == | ||
The underlying open web goal: | The underlying open web goal: | ||
* Open up the webkit-specific part of the web to other vendors in the same way that we had to be practical about what IE-proprietary or IE-only technologies to support. | * Open up the webkit-specific part of the web to other vendors in the same way that we had to be practical about what IE-proprietary or IE-only technologies to support. | ||
== straw proposal == | == straw proposal == | ||
* 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. | * 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 == | == straw proposal downsides == | ||
| Line 29: | Line 59: | ||
== possible downside mitigation == | == possible downside mitigation == | ||
* In the short term we can at least remove pain for web authors and users. | * 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. | * 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 == | == questions and methodology == | ||
| Line 60: | Line 95: | ||
** put the energy first into contributing and passing test suites instead. | ** 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 == | == meetings minutes discussions == | ||
| Line 87: | Line 124: | ||
** .net: [http://www.netmagazine.com/news/css-vendor-prefixes-threaten-open-web-121757 CSS vendor prefixes threaten open web] | ** .net: [http://www.netmagazine.com/news/css-vendor-prefixes-threaten-open-web-121757 CSS vendor prefixes threaten open web] | ||
** WebMonkey: [http://www.webmonkey.com/2012/02/webkit-isnt-breaking-the-web-you-are/ WebKit Isn’t Breaking the Web, You Are] | ** WebMonkey: [http://www.webmonkey.com/2012/02/webkit-isnt-breaking-the-web-you-are/ WebKit Isn’t Breaking the Web, You Are] | ||
** YCombinator Hacker News: "[http://news.ycombinator.com/item?id=3570713 Long experience of contacting sites suggests that it is, at best, of limited effectiveness. ...]" - hoppipolla at Opera on limits of evangelism | |||
* 2012-02-10 | * 2012-02-10 | ||
** Pam Griffith: [http://www.pamgriffith.net/blog/thoughts-on-all-this-vendor-prefix-nonsense Thoughts on all this vendor prefix nonsense] | ** Pam Griffith: [http://www.pamgriffith.net/blog/thoughts-on-all-this-vendor-prefix-nonsense Thoughts on all this vendor prefix nonsense] | ||
| Line 92: | Line 130: | ||
** Web Standards Project: [http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/ Call for action on Vendor Prefixes] | ** Web Standards Project: [http://www.webstandards.org/2012/02/09/call-for-action-on-vendor-prefixes/ Call for action on Vendor Prefixes] | ||
* ... | * ... | ||
* 2012-02-14 | |||
** A List Apart: [http://www.alistapart.com/articles/the-vendor-prefix-predicament-alas-eric-meyer-interviews-tantek-celik/ The Vendor Prefix Predicament: ALA’s Eric Meyer Interviews Tantek Çelik] | |||
* 2012-02-15 | * 2012-02-15 | ||
** Alex Russell: [http://infrequently.org/2012/02/misdirection/ Misdirection] | ** Alex Russell: [http://infrequently.org/2012/02/misdirection/ Misdirection] | ||
** Dylan Wilbanks: [http://dylanwilbanks.com/blog/2012/02/15/vendor-prefixes-and-their-discontents/ Vendor prefixes and their discontents] | ** Dylan Wilbanks: [http://dylanwilbanks.com/blog/2012/02/15/vendor-prefixes-and-their-discontents/ Vendor prefixes and their discontents] | ||
* ... | |||
* 2012-04-25 | |||
** .net: [http://www.netmagazine.com/news/opera-confirms-webkit-prefix-usage-121923 Opera confirms WebKit prefix usage] | |||
* ... | |||
* 2012-04-27 | |||
** Dev.Opera: [http://dev.opera.com/articles/view/opera-mobile-emulator-experimental-webkit-prefix-support/ Opera Mobile Emulator build with experimental WebKit prefix support] - has list of -webkit- properties Opera has decided to support so far. | |||
** WebMonkey: [http://www.webmonkey.com/2012/04/opera-forges-ahead-with-plan-to-support-webkit-prefixes/ Opera Forges Ahead With Plan to Support WebKit Prefixes] | |||
* ... | |||
* 2012-06-04 | |||
** mozilla.dev.platform: [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/itl6mtx2dxI Policy for experimental CSS features in Gecko] - proposal by David Baron | |||
* ... | |||
* 2012-07-03 | |||
** PPK: [http://www.quirksmode.org/blog/archives/2012/07/vendor_prefixes.html Vendor prefixes are fucking batshit crazy] (troll?) | |||
* ... | * ... | ||
| Line 105: | Line 158: | ||
* 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]. | * 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 ... | ** -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 == | == Data on vendor-specific prefixes == | ||
| Line 183: | Line 236: | ||
Summary [https://bug708406.bugzilla.mozilla.org/attachment.cgi?id=596728 data] is attached to [https://bugzilla.mozilla.org/show_bug.cgi?id=708406 bug 708406]. | Summary [https://bug708406.bugzilla.mozilla.org/attachment.cgi?id=596728 data] is attached to [https://bugzilla.mozilla.org/show_bug.cgi?id=708406 bug 708406]. | ||
[[Category:Web Compatibility]] | |||