One of the things that's different about how we operate in Chromium vs. other engines is that we force our teams to work in public and ask for feedback as early as plausible. "Intent to Implement" is many, many miles away from shipping on-by-default to Stable in our process.https://twitter.com/slightlylate/status/1139031140415623168 …
First, it's not "Google", it's engineers on the team trying to solve a problem, usually in concert with one or more partners who have a need (which the Explainers should outline; see template: https://github.com/w3ctag/w3ctag.github.io/blob/master/explainers.md …) Next, it's much easier to respond to concrete proposals...
-
-
Explainers start with problems and, when they're posted in these forms, are *super* malleable. They're basically "logs of ideas we had and our best guesses thus far", including considered alternatives.
-
Those documents evolve over time as folks collaborate to get to solutions that can work for everyone who has the set of problems outlined at the top.
End of conversation
New conversation -
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.