> the `input` event would have the default behavior of full cloning Hm, it feels like, when the selected option is changed via user interaction, the <selectedo

> the `input` event would have the default behavior of full cloning Hm, it feels like, when the selected option is changed via user interaction, the <selectedoption> should be populated before the event fires. But this is really besides the point, because not all selected-option-changes come with an input event, eg programatic change, including to the content of the currently selected option, which the post focuses on. > that leaves many edge cases like multiple `<selectedoption>` elements I believe That isn't really a big problem. It's something the platform already deals with all over the place, like multiple <title> elements, multiple elements with the same ID etc etc.