What information was incorrect, unhelpful, or incomplete?
The DOM spec is being updated to change when Range.deleteContents() and the extract algorithm (used by Range.extractContents()) collapse the range to (newNode, newOffset). The collapse now happens before DOM mutations rather than after, so that the DOM's built-in live range maintenance mechanisms keep the range valid through subsequent operations.
What did you expect to see?
Documentation should reflect that the range is collapsed before mutations are performed, matching the updated spec.
Related
Do you have any interest in resolving this?
No (this is primarily a spec-level change; the observable behavior is the same in current browsers since no removing step currently fires synchronous script).
What information was incorrect, unhelpful, or incomplete?
The DOM spec is being updated to change when
Range.deleteContents()and theextractalgorithm (used byRange.extractContents()) collapse the range to(newNode, newOffset). The collapse now happens before DOM mutations rather than after, so that the DOM's built-in live range maintenance mechanisms keep the range valid through subsequent operations.What did you expect to see?
Documentation should reflect that the range is collapsed before mutations are performed, matching the updated spec.
Related
Do you have any interest in resolving this?
No (this is primarily a spec-level change; the observable behavior is the same in current browsers since no removing step currently fires synchronous script).