- From: Jonathan Kew <jfkthame@gmail.com>
- Date: Thu, 17 Sep 2015 18:47:34 +0100
- To: Greg Whitworth <gwhit@microsoft.com>, "mmaxfield@apple.com" <mmaxfield@apple.com>
- Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, David Baron <dbaron@dbaron.org>, Dean Jackson <dino@apple.com>, Tab Atkins <tabatkins@google.com>, "www-style@w3.org" <www-style@w3.org>
On 17/9/15 18:08, Greg Whitworth wrote: >>> The corresponding Gecko change in https://bugzilla.mozilla.org/show_bug.cgi?id=1099557 should appear in Nightly builds in a day or two, >> and is currently aimed to ship in Firefox 43 (mid-December). So that will coordinate well with Chrome 47. >>> JK > > >>> I've created a WebKit bug for this at https://bugs.webkit.org/show_bug.cgi?id=149128 >>> -- Myles > > Awesome thanks to you both!! > You're welcome. Note, however, that the timeline suggested in your message yesterday: # TPAC 2015: All UAs have code in their browsers behind flag (off by # default) # TPAC 2015 - Summery or Fall 2016: PR from all UAs devrel, tooling, # etc regarding breaking change # Now - Early 2016: UAs do internal testing, testing via dev channels # (if available), testing with third parties and report back any compat # issues found to www-style thread # Summer or Fall 2016: Find shipping date that can overlap as many UAs # as possible as not to make it so that one UA has to carry the burden # of "bugs" is substantially different from what I understood Blink to be aiming at (shipping at the beginning of Dec), and followed for Gecko (FF43, ships mid-Dec). Should we be holding back from those planned dates? E.g. shipping this on Nightly and Developer Edition only for the time being? Tab, can you confirm the timeline for this in the Blink world? JK
Received on Thursday, 17 September 2015 17:48:04 UTC