Again, that's categorically not what happened here (because our process works to prevent it). Follow the links and look at the evidence: https://github.com/w3ctag/design-reviews/issues/308 … https://groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/irhrlr6n5YQ/LOS8xSGsBwAJ …https://groups.google.com/a/chromium.org/forum/m/#!topic/blink-dev/gL2EVBzO5og/discussion …
The Blink Launch Process is conscious of this history and does not gate on formal standards phases, but takes a risk-based approach to interop.
-
-
As before, one has to wonder why you couldn’t just ship behind a flag, with a provided polyfill, *until* those two interoperable implementations existed. Ideally there’s a better answer than “we wanted it now and others weren’t moving fast enough.”
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.
