1 Commits (c894afd8c73e4f08a377909f29aa58177a256277)

Author	SHA1	Message	Date
Paolo Ricciuti	06c9b7929a	fix: prevent `selectedcontent` mutation from changing the selected option (#18495) ... Basically, in a situation like this ```svelte <script lang="ts"> let value = $state('A'); </script> <input oninput={() => {}} /> <select bind:value> <button><selectedcontent></selectedcontent></button> <option>A</option> <option>B</option> <option>C</option> </select> <style> select,::picker(select){ appearance: base-select; } </style> ``` what happens is that the `oninput` is delegated and so it registers the global listener (which means it listen on every `oninput` not just the one from the input). When the select change, the `input` event is dispatched first, the listener runs, doesn't find an `__input` handler and returns. Now before the `change` event is emitted, the `MutationObserver` in `init_select` is triggered by the browser updating `selectedcontent` and invokes `select_option` with `select.__value`. However, since the `change` event has yet to fire, `select.__value` still has the old value, so we "reselect" that. When the change event runs, the selected option is effectively the old one and the whole thing breaks. I had to add the test in `runtime-browser` because JSDom doesn't support `selectedcontent`	1 week ago