- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 23 Sep 2015 16:54:07 -0700
- To: Jonathan Kew <jfkthame@gmail.com>
- Cc: www-style list <www-style@w3.org>
On Tue, Sep 22, 2015 at 12:48 AM, Jonathan Kew <jfkthame@gmail.com> wrote: > 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
Received on Wednesday, 23 September 2015 23:54:54 UTC