Rationale: all design systems have these things. But there's no native HTML way, so we fake it with loads of JS. That needs loads of ARIA. And, unless you really really know what you're doing, it's easy to make things worse with ARIA.
-
Show this thread
-
The mighty brains of
@briankardell,@stevefaulkner,@LeonieWatson and@chaals came up with this interesting proposal a while back https://bkardell.com/common-panel/index.src.html … - time to revive it?3 replies 0 retweets 14 likesShow this thread -
Replying to @brucel @briankardell and
Why not some flavor of a "stdlib" of web components maintained like specs would be? User agents could pre-cache it, update opportunistically, etc.
1 reply 0 retweets 3 likes -
Replying to @fabricedesre @brucel and
Google tried to propose a vision forward which was basically this. It made for some good experiments and discussions but I'm not sure that's going forward at all now. There are complex reasons. Nothing is as simple as you'd expect.
1 reply 0 retweets 2 likes -
Replying to @briankardell @fabricedesre and
A lot of the background of such can be eventually followed to through discussion and links fromhttps://github.com/w3ctag/design-reviews/issues/384 …
1 reply 0 retweets 5 likes -
Replying to @briankardell @fabricedesre and
I believe that at a minimum, Google deserves some good faith credit here for trying to lay out a whole vision for discussion. Think it could have been presented slightly better, but even if it didn't pan out, big props to
@domenic and others for trying hard/starting conversations1 reply 0 retweets 9 likes -
Replying to @briankardell @fabricedesre and
In retrospect, the pushback against toast was a good sign that any attempts at rallying around standard high-level controls will not succeed. I'm doubtful anyone can overcome that kind of negativity e.g. for accordion.
3 replies 0 retweets 6 likes -
Replying to @domenic @briankardell and
I think when you present something as well-researched as https://github.com/jackbsteinberg/std-toast/tree/master/study-group … and get https://adrianroselli.com/2019/06/scraping-burned-toast.html … in response, browser vendors are going to be very hesitant to invest any time in the controls listed in the OP of this thread.
7 replies 1 retweet 19 likes -
Replying to @domenic @briankardell and
And to think the drama involved in WC may have been the "easy" path
No responsible platform vendor asks their engineers to take lkml-levels of abuse.2 replies 0 retweets 5 likes -
Replying to @slightlylate @domenic and
I think the wrong lesson may have been learned here. If “Intent to Prototype” naming had been in place from the beginning, I think toast would still be alive today. IMO, this really was 100% about ppl wrongly saying, “Google’s making toast without asking anybody else’s opinion!”
4 replies 0 retweets 7 likes
How about we let another team walk into the firing line and find out? I'm not gonna keep volunteering our people wade into a toxic rhetorical cesspool.
-
-
Replying to @slightlylate @dfabu and
They asked me something to the effect of "we know you said it was going to be near impossible to add to HTML back in '11, but do you think things have died down and it might be safe now?" I regret indicating it might be ok to try w/ enough research to back it up.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @dfabu and
But need looks well researched to me. And I don't have to have gobs of experience to see why we should resolve with a relatively straightforward element so there's not 9 different ones across a variety of FWs and libraries.
0 replies 0 retweets 3 likes
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.