in both of those cases it is the responsibility of the HTML author.
-
-
Replying to @briankardell @prushforth and
Or <select custom-foo>. is= isn't the only possible solution to this problem. Time to back something different.
1 reply 0 retweets 2 likes -
Replying to @matthewcp @briankardell and
Certainly we've been stuck on is, but I never understood the confusion, especially when you're talking about kids as HTML authors. KISS.
1 reply 0 retweets 0 likes -
Replying to @prushforth @matthewcp and
One issue with <select> is all browsers will need to re-implement it in terms of Shadow DOM. Some els do this today, not all.
1 reply 0 retweets 1 like -
Replying to @rob_dodson @prushforth and
That would let developers actually restyle the internals. That means standardizing what those internals look like.
2 replies 0 retweets 3 likes -
Replying to @rob_dodson @prushforth and
That's the conclusion I'm arriving at, too. But that's a formidable challenge, and involves speccing UI which browser vendors hate
3 replies 0 retweets 1 like -
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 @slightlylate @brucel and
Like, if you could pick out the behaviors you wanted from <select> and just re-use a large fraction of them, would make CE easier to build
1 reply 0 retweets 2 likes -
Replying to @slightlylate @brucel and
Would be useful. Would be better if we could use that *with* <select>.
1 reply 0 retweets 0 likes -
Replying to @prushforth @slightlylate and
i.e. get the parsing behaviour, but only the active behaviour we choose.
2 replies 0 retweets 0 likes
I hear what you're saying, but what I'm trying to flag is that getting something useful accomplished often means routing around opposition
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.