Reference the move primitive in DOM mutations section #341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: I don't think is ready to merge yet; I'd consider it blocked on whatwg/dom#1307.
The whatwg/dom#1307 PR in the DOM Standard introduces a new "move" primitive, and this Selection API PR modifies this specification reference the "move" primitive in the section about responding to arbitrary DOM mutations. This PR does not specify exactly how the selection should be modified during DOM mutations, but rather obliquely references the effects that "insert" and "remove" have on the Range that the visual selection is based off of. This PR makes this more clear, by indicating that the real work relevant to the on-screen selection is delegated to the Range-updating logic in those DOM primitives, including the "move" primitive.
For normative changes, the following tasks have been completed:
Editing WG resolution on the proposed changes, with at least two implementers participating and not objecting:
For browsers that are shipping the feature, implementation bugs are filed for the proposed changes (link to bug, or write "Not Implementing"):
Preview | Diff