That's the conclusion I'm arriving at, too. But that's a formidable challenge, and involves speccing UI which browser vendors hate
-
-
Replying to @brucel @rob_dodson and
I'm somewhat more optimistic about a related project: de-composing all the behavior of the built-in elements into reusable mixins.
2 replies 0 retweets 5 likes -
-
Replying to @brucel @rob_dodson and
Nope. Have discussed at TAG, but it's a huge undertaking.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @brucel and
I think we need to come up with a good story for styling as well - if everything is jammed into shadow dom by default we end up at square 1
1 reply 0 retweets 5 likes -
Replying to @sundress @slightlylate and
So need to figure out how theming works and maybe reify that as well?
1 reply 0 retweets 2 likes -
My approach here would be the same: smuggle all the useful contracts out of the built-ins until such time as we can explain all the behavior
2 replies 0 retweets 2 likes -
Replying to @slightlylate @brucel and
I don't think a good styling story currently exists? What good bits are you referring to?
2 replies 0 retweets 0 likes -
Oh, styling isn't great and probably can't be fixed until last. But we can make re-building your own <select>-alike painless.
2 replies 0 retweets 0 likes -
Replying to @slightlylate @brucel and
Yes but until the styling story works people will keep reimplementing and doing it badly
1 reply 0 retweets 1 like
They're doing it badly, in part, because the cliff is so tall. So much to re-implement and so little help from us.
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.