> now we are going to have a `button` in `select` with a `selectedoption` tag? Can you detail why this is such an awful thing? > The CSS for the style of the

> now we are going to have a `button` in `select` with a `selectedoption` tag? Can you detail why this is such an awful thing? > The CSS for the style of the element belongs with the `select` tag That isn't even true today. A select is made up of multiple parts, the button that's always visible on the page, and the resulting menu/popover which contains multiple options. These can already be styled a bit depending on the platform. However, folks want to style them in more detail, and as a result they end up having to recreate a select from scratch, and in almost all cases they mishandle the keyboard navigation and accessibility. The aim here is to provide the freedom of styling whilst providing good keyboard and accessibility out of the box. > I get the sense that the people currently working on HTML and CSS are front-end designers and not programmers. I'm sorry to tell you that your sense is way off. The strongest voices in web standards are browser engineers, who tend to be more familiar with C++ than building web apps/sites. This is why we need to ensure that web developer voices are heard in these discussions, hence the post.