- From: Greg Whitworth <gwhit@microsoft.com>
- Date: Wed, 20 Apr 2016 18:53:00 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, Jonathan Kew <jfkthame@gmail.com>, Simon Fraser <smfr@me.com>
- CC: www-style list <www-style@w3.org>
>> On 21/9/15 18:49, fantasai wrote: >>> On 09/21/2015 11:54 AM, Greg Whitworth wrote: >>>> It's fine if they ship on stable, but they should still be behind a >>>> flag that is off by default. We need to ensure there is little to no >>>> substantial compat risk, and then ship with it on by default in >>>> stable builds after giving web developers the heads up of the >>>> breaking change (we're thinking late 2016). >>> >>> >>> If Chrome and Firefox are comfortable doing a coordinated release in >>> December, I don't think we need to hold them back. If they're not, we >>> can of course go with a longer timeline to loop in Microsoft and >>> Apple. >> >> Tab: can we get an update on the Chrome team's plans here, please? As >> of now, we're on track to ship this (i.e. ON-by-default) in Firefox on >> the release channel in December; but will put it back behind an >> OFF-by-default flag if the longer timeline is preferred. > >I just talked to our implementor - the plan right now is for it to ship in Chrome >47 (early Dec) flagged off, then flag on in 48 (mid-Jan). > >~TJ Following up here, this is currently behind a flag on Firefox/MS Edge and doesn't seem to be in Chrome. I'm currently not sure about Safari, any updates here. Remember that we had a tentative agreement to get this behind a flag by November of 2015 and then determine a ship timeframe that worked for all vendors. Thanks, Greg
Received on Wednesday, 20 April 2016 18:53:30 UTC