Re: [whatwg/dom] Atomic move operation for element reparenting & reordering (Issue #1255)

Implementation details aside, the specifics of how `moveBefore()` is implemented may have downstream effects in the browser and platform accessibility trees. It's too soon to tell, but effectively that could mean this may not be state preserving for accessibility elements, effectively similar to remove/insertBefore... which usually results in a destroyed accessibility element, and a newly created one with a different unique ID.

Speculative implementors on all platforms, please coordinate with the engine accessibility DRIs for your engine. Listing some starting points here.

Chrome: @aleventhal 
Firefox: @jcsteh
Edge: @benbeaudry

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

Message ID: <whatwg/dom/issues/1255/2438705796@github.com>