Re: [whatwg/dom] Meta: a list of side effects that would be impacted by state-preserving move (Issue #1270)

> I believe this would also affect [being-rendered](https://html.spec.whatwg.org/multipage/rendering.html#being-rendered), whose exhaustive implications I am not sure.
> 
> * At least [`<object>`](https://html.spec.whatwg.org/multipage/iframe-embed-object.html#the-object-element:being-rendered) and  [`<embed>`](https://html.spec.whatwg.org/multipage/iframe-embed-object.html#concept-embed-active)[1](#user-content-fn-1-ddfe52531399d0901c414136eb7bd0e4) would be affected.
> * It might have effect on `<img>` element that [allow auto-size](https://html.spec.whatwg.org/multipage/embedded-content.html#allows-auto-sizes), though I'm really not sure here.
> * That might also affect `<select>` and `<input>` elements on which `showPicker()` has been called, keeping some pickers alive.
> 
> ## Footnotes
> 1. Though the specs for `<embed>` are a bit weird and ask the checks are made against the state at the first step of the event loop. But browsers [do agree](https://jsfiddle.net/h39nbwzo/) that moving it around in the DOM does trigger a reload, even if the move has been completed in the same EL iteration. [↩](#user-content-fnref-1-ddfe52531399d0901c414136eb7bd0e4)

Thanls, added these!

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/1270#issuecomment-2036614438
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/dom/issues/1270/2036614438@github.com>