#SadButTrue “In browsers many interactive elements cannot be styled as desired by web developers” http://www.paciellogroup.com/blog/2015/02/emulating-failure/ … /thx @codepo8
-
-
Replying to @mahemoff
This is why elements like custom dropdowns have to be reinvented by 3rd party libraries. Web Components is amazing but doesn’t solve this.
1 reply 0 retweets 1 like -
Replying to @mahemoff
@mahemoff Yes, this still bothers me as well. It feels like platform 101: extend native controls and style as needed. +cc@slightlylate4 replies 0 retweets 2 likes -
Replying to @aerotwist
@aerotwist@mahemoff@slightlylate extend as in Win32 subclassing, as in Shadow DOM, or as in Silverlight XAML?1 reply 0 retweets 0 likes -
Replying to @thespite
@thespite@aerotwist@slightlylate Even just following CSS, e.g. <select> paying due respect to align, font-weight etc would go a long way.1 reply 0 retweets 2 likes -
Replying to @mahemoff
@mahemoff@thespite@aerotwist : these elements are a write-off. Too much legacy. What we need is full-fidelity ability to replace.1 reply 0 retweets 0 likes
@mahemoff @thespite @aerotwist : if legacy didn't sink you, browser bugs would. Demand the power to *make*, not "save", <select>
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.