The fact they're not is probably hurting accessibility and usability a ton, since just about every individual and business wanting stylistic consistency is stuck reinventing the wheel with 'fake' versions or JavaScript.
Or are you trying to keep the status quo, where people hack some shit out of divs that you can't change the appearance?
I believe firefox got this natively after greasemonkey died, but I never looked how to do it.
In Sciter, all input elements are ordinary styleable primitive DOM elements. <select> is there too so you can style it in the way you want:
select {...}
select > caption {...}
select > button {...}
select > popup {...}
select > popup > option {...}
Such composition goes even further. <option>s, for example, may have arbitrary content as also you can apply built-in DOM element controllers to DOM structure of your choice.This for example is a table that behaves as a <select type="list"> with rows-options:
<table>
<tbody style="behavior:select-list; overflow-y:auto;">
<tr role="option" value="A"><td><td></tr>
<tr role="option" value="B"><td><td></tr>
</tbody>
</table>Calling the problem "aesthetics" though is too narrow. There are numerous things people would like to see in a native select:
- Optional search/filtering of options (without the need for an input field and JavaScript wiring).
- Being able to style.
- HTML in an option for example multi-line options.