the <toast> element proposal is such a perfect illustration of the incentive structure bred by the internal Google dynamics around the Mobile Webhttps://twitter.com/jensimmons/status/1138980859728531456 …
-
Show this thread
-
toasts aren't even a thing on other platforms, it's specifically an Android thing (sure, the UI concept exists, but it's only Android that calls it a toast)
5 replies 2 retweets 28 likesShow this thread -
The proposal does have merit: it probably would be good for screen readers (though <dialog> or aria role=dialog probably suffices? maybe?) but that's not really front-and-center, it's "developers might get this wrong" (which is what libraries are for)
2 replies 0 retweets 9 likesShow this thread -
to think Google pushed super hard on Custom Elements -- to the point of jumping the gun on shipping, ending up with an incompatible shipped version-- to not use it as the primary path for situations like these
1 reply 1 retweet 25 likesShow this thread -
Replying to @ManishEarth
I heard they always use flags to prevent forging de facto standards. Not in CE’s case?
1 reply 0 retweets 1 like -
Replying to @BrendanEich
I'm not sure exactly what happened; but "custom elements v0" got used quite a bit, especially on Google properties. YouTube was using v0 (with a slow polyfill for other browsers) for years after v1 shipped
1 reply 1 retweet 3 likes -
-
Replying to @BrendanEich @ManishEarth
I don’t know the history of custom elements sorry, perhaps
@slightlylate ?1 reply 0 retweets 0 likes -
We shipped v0 Web Components in 2014 after multiple years of attempting to collaborate with basically everyone. Weren't many choices & hadn't yet invented Origin Trials (see blog post from '15: https://infrequently.org/2015/08/doing-science-on-the-web/ …)
2 replies 1 retweet 7 likes -
Replying to @slightlylate @erikcorry and
Your phrasing sounds like other vendors were simply ignoring WC. This wasn't the case. Mozilla had actually started on a v0 implementation in 2013 (see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=806506 …).
2 replies 0 retweets 9 likes
...staffed at a low level at that point and didn't move forward for opaque reasons. Frustrating for everyone.
-
-
Replying to @slightlylate @erikcorry and
One reason is that it became clear there wasn't consensus around v0, especially from Apple.
0 replies 0 retweets 2 likesThanks. 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.