3 ms·
> <select> is good enough for me, [...] If it just was fully styleable. Browsers really should implement better selection of customizable standard widgets. Cur
by Yaggo 9y ago
> <select> is good enough for me, [...]
If it just was fully styleable. Browsers really should implement better selection of customizable standard widgets. Currently it requires too many hacks to re-style the built-in input elements. Web components feel a bit overkill for most cases.
- colejohnson66 9y agoDidn’t IE use to let you style random components such as even the scroll bar?
- Yaggo 9y agoMost if not all major browsers let you style scrollbars, but the problem is that styling for built-in widgets is not standardized, i.e. it relies on vendor prefixes and worse, not all (sub) elements can be styled at all depending on browser. E.g. <select> has poor support for styling.
- frou_dh 9y agoYep - I remember on vBulletin forums, the native vertical scrollbar often got the same vibrant colouring as the forum's theme.
- noisem4ker 9y agoOr maybe designers should learn to respect the platform's widgets' look and feel, which the user is familiar with and has possibly customized according to their preferences and accessibility needs.
- oblio 9y agoHah! You're kidding, right? Custom styling or "skins" has been one of the main drivers of app development since the beginnings of time. I feel that we, puritans, should just give up and accept what the masses want.
- Yaggo 9y agoUnfortunately the industry just doesn't work that way. Accessibility is one reason why css-themeable native widgets would be a win for everyone, their look will match with the branding (customer happy) and behaviour will be consistent (end user happy), and standardization would make developers happy.