A few thoughts on <std-toast> and Google’s approach to web standardshttps://gist.github.com/dauwhe/065b0c2b4ffae7b00e103e63edab25b9 …
-
-
Replying to @dauwhe
FWIW and not claiming Chrome consensus on this, I agree that the WICG thread should be noticeably before the I2I, and I think there should be enough interest to move the repo into the WICG before the I2I. That doesn't necessarily mean cross-browser interest.
1 reply 0 retweets 2 likes -
There's no central review for creating I2I or I2S threads, so we have no way to prevent threads that violate even the consensus process. The best we can hope for is that the replies point out violations.
1 reply 0 retweets 1 like -
This all seems somewhat too speculative. What's the "cool down" period we should demand for I2I? And why?
1 reply 0 retweets 0 likes -
I2I isn't "fire-and-forget", it's "I'm gonna try something out that could still fail fast, and I plan on iterating". Our process is markedly different that what it seems many who are not looking closely seem to assume it is.
1 reply 0 retweets 1 like -
Replying to @slightlylate @dauwhe
Mhmm, I'm suggesting that we ask people to have a design and do a tiny bit of outreach before starting to implement. The bar for getting something into a WICG repository is low ("sufficient interest is shown in the discourse"—https://github.com/WICG/admin#contributing-new-proposals … ), so it shouldn't take long.
1 reply 0 retweets 0 likes -
What problem would that solve?
1 reply 0 retweets 1 like -
It would let external folks see the work teams are already doing to validate that there's a feature to build in this area. It would help make sure that teams don't start implementing something that has absolutely no chance of success, although teams don't actually do that.
2 replies 0 retweets 0 likes -
I think
@domenic made an important point today: “We’d so far only spoken to UI engineers or people who work on design systems…” Having a more diverse group of people looking at a proposal earlier seems to help uncover potential issueshttps://github.com/jackbsteinberg/std-toast/pull/30#issuecomment-501841140 …1 reply 0 retweets 1 like
so it's good that this is all open early so we can get (and address) all of that feedback!
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.