Gregory's Server@jaffathecake Definitely not an expert here, but from a framework perspective, I think "Option: Nothing by default, but provide a way to trigger an update" is fine? In Angular you could do that like:
```
afterRender(() => {
selectedContent.resetOption();
});
```
(Could probably be more specific by effect-ing the selected option specifically.)
Either way of automatically resetting content seems bad for the performance and scheduling reasons you specified. Even if it was debounced, each framework schedules renders in different ways, so having it update at a different time is a recipe for bugs.
Targeted, automatic updates sounds cool, is that realistic to browser vendors though?
Honestly I expect most framework users would be better off not using `<selectedoption>` and just letting the framework manage rendering the content in multiple places. Frameworks already have decent solutions for that.
Maybe it's best to keep this simple and just expect more advanced use cases to skip the element entirely?
@jaffathecake I wonder if there's a path to something like shadow DOM slots? In that context you can "project" an element from one location to another. What if the browser did a similar trick but which duplicated the element visually, while still only having one element in the DOM? Similar to how projected light DOM is not *in* the shadow DOM, it has a slot linked to the light DOM.
That feels similar to your last option but maybe would be more feasible to browser maintainers? It might require it's own spec independent of styled `<select>` though.
I wonder if that would help with something like `<canvas>`, since you could keep the same visual content in both copies, as there is only one source of truth. Doing this with an iframe sounds weird and scary though, so maybe it's a bad idea.
@jaffathecake I wonder if there's a path to something like shadow DOM slots? In that context you can "project" an element from one location to another. What if the browser did a similar trick but which duplicated the element visually, while still only having one element in the DOM? Similar to how projected light DOM is not *in* the shadow DOM, it has a slot linked to the light DOM.