canmove, Confirmed users
2,887
edits
Platform/Layout/CSS Compatibility: Difference between revisions
Jump to navigation
Jump to search
summary at top, new WebMonkey article
(→problematic sites: tracking bug) |
(summary at top, new WebMonkey article) |
||
| Line 1: | Line 1: | ||
= CSS vendor-prefix compatibility = | = CSS vendor-prefix compatibility = | ||
'''Problem: WebKit mobile web monoculture.''' There is currently 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 likely, on properties Mozilla deems necessary according to our [https://bugzilla.mozilla.org/show_bug.cgi?id=708406 study of -webkit- dependent sites]. | |||
'''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]. | |||
__TOC__ | |||
== problem statement == | == problem statement == | ||
| Line 19: | Line 36: | ||
== 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 | |||
** CSS3 Transitions | |||
** CSS3 Transforms | |||
* Consider implementing some -webkit- prefixed properties. | * Consider implementing some -webkit- prefixed properties. | ||
** Experiment with implementation and see if that fixes sites (the efficacy test). | |||
== straw proposal downsides == | == straw proposal downsides == | ||
| Line 99: | Line 121: | ||
** 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-27 | |||
** 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] | |||
* ... | * ... | ||