Hi Rich, I run standards for Chrome. If you'd like to discuss our approach, happy to set up a call.
-
-
Replying to @slightlylate
Would it result in changes to how you do things, so that web developers are spared further episodes like this one?
4 replies 0 retweets 112 likes -
Replying to @Rich_Harris @slightlylate
Serious question: Why would this change “break the web” ? Constructable stylesheets are behind a flag, since they’re non-standard, right? Why can’t they be changed at this point? There’s never an expectation of stability when stuff is behind a flag, right?
1 reply 0 retweets 18 likes -
Replying to @AdamRackis @Rich_Harris
They're shipped to stable Chrome (and many Chromium embedders enable them too).
2 replies 0 retweets 0 likes -
Replying to @slightlylate @Rich_Harris
As the person who runs standards for Chrome, can you please explain how the fuck a non-standard feature got shipped to Stable Chrome?
1 reply 0 retweets 32 likes -
Replying to @AdamRackis @Rich_Harris
We often lead, balancing risk/reward rather than demanding a particular point in an arbitrary process. https://www.chromium.org/blink/launching-features … Leadership is rather the point of having an engine team, after all.
4 replies 0 retweets 4 likes -
Given that chrome has a near monopoly don't you think you should maybe not ship something as stable before other browsers have it to not reinforce the monopoly?
2 replies 0 retweets 13 likes -
These situations arise only after we: - design in public - beg for feedback (which we usually don't get in a timely way) - write the specs *and* the tests - send designs for wide review - (usually) experiment (via OT) for multiple releases
2 replies 0 retweets 4 likes -
Was Safari’s feedback that the race condition around adding stylesheets was a “show stopper” before, or after this was shipped to Chrome Stable?
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @slightlylate and
Just came here to say: if you're going to beat up on companies and individuals at companies for trying to make things better, we'll end up with a stagnant ecosystem.
2 replies 0 retweets 6 likes
Also, we have an impl that works well. Folks can make "showstopper" claims, but the proof is in the pudding. Note: other vendors are not building and testing alternatives. Talk is cheap.
-
-
Replying to @slightlylate @davidbrunelle and
Remember the grandstanding around "type 2+ encapsulation" for SD and how it wasn't worth pursuing w/o it? Stop-energy comes in many forms. Watch who's writing code and making things (safely) available to test.
1 reply 0 retweets 1 like -
Replying to @slightlylate @davidbrunelle and
We also have a well proven path for making breaking changes. When others feel the design we shipped is wrong, they can ship the "right" design, and if we find it to also be reasonable we can ship it too and push the ecosystem to migrate to the more broadly supported form.
1 reply 0 retweets 2 likes - 8 more replies
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.