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. JKReceived on Tuesday, 22 September 2015 07:49:30 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:57 UTC