3 ms·

Thanks for the feedback! Fwiw, there's no point populating <selectedoption> yourself. Just don't use <selectedoption>. It's optional. That's probably what I'd d

• dfabulich 2y ago
  Good to know. Say, is there a bug in Chrome Canary 132? When I opt into customizable <select>, "change" events stop firing. <style> select, ::picker(select) { appearance: base-select; } </style> <select> <option value="one">one</option> <option value="two">two</option> <option value="three">three</option> </select> <script> document.querySelector('select').addEventListener('change', e => { console.log(e); }) </script> And another. When I add <selectedoption>, I get a warning in the console, "A descendant of a <select> does not follow the content model. <selectedoption> one </selectedoption> " <style> select, ::picker(select) { appearance: base-select; } </style> <select> <button><selectedoption></selectedoption></button> <option value="one">one</option> <option value="two">two</option> <option value="three">three</option> </select>
  • jaffathecake 2y ago
    Those sound like bugs but I'm not really familiar with the implementation. I haven't played with it much either. I'm just an outsider interested in the feature design.