Daniel, Mike, and the whole compat team, thank you for diligently figuring out all the nasty details here and pushing this contentious "feature" forward.
This is a tough balance for the good of our users, and I'm grateful for all the thought and careful consideration you have put into it. We noted a high level intent to consider doing this at the CSSWG f2f nearly two years ago, and as this lands I'm sure it will come up again at the next f2f. dbaron and I will be there to support your work. Tantek On Thu, Dec 31, 2015 at 12:40 AM, Jonas Sicking <jo...@sicking.cc> wrote: > Yay! > > (I agree that it's sad that we need to do this, but still "yay" for > being more compatible with the web). > > / Jonas > > On Wed, Dec 30, 2015 at 10:40 PM, Daniel Holbert <dholb...@mozilla.com> wrote: >> Summary: >> A good chunk of the web today (and particularly the mobile web) >> effectively relies on -webkit prefixed CSS properties & features. We >> wish we lived in a world where web content always included >> standards-based fallback (or at least multiple-vendor-prefixed >> fallback), but alas, we do not live in that world. To be successful at >> rendering the web as it exists, we need to add support for a list of >> frequently-used -webkit prefixed CSS properties & features. >> Every other major modern browser engine implements support for these >> aliases -- Blink & WebKit obviously have them, & Edge includes them for >> compatibility. (I'm not sure about IE's support, but it's not a >> particularly important data point, given that Microsoft is focused on >> Edge going forward.) >> >> Bug tracking implementation: >> https://bugzilla.mozilla.org/show_bug.cgi?id=1170789 >> >> Bug to enable pref: >> https://bugzilla.mozilla.org/show_bug.cgi?id=1143147 >> (Will likely land in the next few days.) >> >> Link to standard: >> Mike Taylor is working on a WHATWG spec describing the -webkit >> prefixed features that we believe are needed for web compatibility. >> That spec lives here: http://compat.spec.whatwg.org/ >> There's also been some discussion on the CSSWG mailing list about >> updating official CSS specs to mention legacy -webkit aliases (and >> discourage authors from using them), as discussed in this thread: >> https://lists.w3.org/Archives/Public/www-style/2015Dec/0132.html >> >> Platform coverage: >> All platforms. >> >> Estimated or target release: >> Firefox 46 (current Nightly), or 47 if we need to hold it back a >> release to fix things. >> >> Preference behind which this will be implemented: >> layout.css.prefixes.webkit >> >> Side note on earlier work: >> Earlier this year, in bug 1107378, we shipped an experimental JS-based >> version of this feature, which was only active for a whitelist of sites >> (all of which strongly depend on webkit prefixes for usability). This >> experiment proved successful at making the whitelisted sites usable in >> Firefox. The new implementation (behind "layout.css.prefixes.webkit") >> will supersede the older experimental JS-based implementation and will >> not be whitelisted. >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
