Wondering if promoting use of native #HTML5 UI features over custom UI is akin to pissing in the wind?
-
-
Replying to @stevefaulkner
@stevefaulkner I think you should crack on anyway. We need to make existing UI elements properly styleable so we don't have to fake them.1 reply 0 retweets 0 likes -
-
Replying to @stevefaulkner
@stevefaulkner Right, but the solution is not to throw everything that works properly and let authors do (break) whatever they want.1 reply 0 retweets 0 likes -
Replying to @booshtukka
@booshtukka I agree, but web devs will do what they do...1 reply 0 retweets 0 likes -
Replying to @stevefaulkner
@stevefaulkner Because they have to. They are told "we need a <select> like this" by the people who pay them. They have no proper options.3 replies 0 retweets 0 likes -
Replying to @booshtukka
@booshtukka right, I keep hearing from implementers that it's a very hard problem to solve /cc@slightlylate2 replies 0 retweets 1 like -
Replying to @stevefaulkner
@stevefaulkner I hear the same. But we still need to solve it. Even if it means having web components that become part of the spec.1 reply 0 retweets 0 likes -
Replying to @booshtukka
@booshtukka one suggsted path is extending native elements http://w3c.github.io/webcomponents/spec/custom/#semantics …, but that appears to be a non starter2 replies 0 retweets 0 likes
@stevefaulkner @booshtukka : some value in being able to change UI. I'd rather see native els broken down into mixins you can reuse
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.