Re: [csswg-drafts] [css-forms] <select/> field pseudoelements

I think, the look of `<select/>` should be standardized. I saw one example in W3C specification (I cannot recall which). The `<select/>` was drawn like "old windows" style COMBOBOX with arrow. I think, if this element have not arrow in any browser, there should be bossibility to add it. The ::dropdown-list is present in all browsers with GUI. I want have possibility to set option height to 40px to make the element easy tappable. I also want to style it to look like part of created website. 

Many people has problem with it. Please read anou horrible hacks on stackoverflow. What if the arrow will be in left corner of the select? It will not cut by parent overflow:hidden setting.  

I also open topic for [`<datalist/>`](https://github.com/w3c/csswg-drafts/issues/2198). The same problem. But.... In definition `<datalist/>` IS NOT replaced element. The same problem - cannot style look of the dropdown. 

The people that want ot have a site, they cannot grasp, the `<select/>` is replaced element. **They say: "the element is part of my website. This must look like in my graphic project. Make something with it"**. Then I must make **"horrible hacks" with series of radiobuttons and labels and tons of CSS for them**... 

It is high time to standardize look of controls and define pseudoelements. Why we want to style buildin video player (also replaced element - time-related selectors) but not `<select/>`?

BTW. More problem is to REMOVE the ::dropdown-arrow. If you want to add it, you can use any svg as background. Big problem is also write styles for select>option element (change of element size, maximum height, colors, borders...).  

-- 
GitHub Notification of comment by Nadya678
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2013#issuecomment-359447184 using your GitHub account

Received on Monday, 22 January 2018 14:56:11 UTC