Note: I don't think is ready to merge yet; I'd consider it blocked onwhatwg/dom#1307.

Thewhatwg/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:

  • WebKit
  • Chromium
  • Gecko

• For browsers that are shipping the feature, implementation bugs are filed for the proposed changes (link to bug, or write "Not Implementing"):

  • WebKit (https://bugs.webkit.org/show_bug.cgi?id=)
  • Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=)
  • Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=)

Preview |Diff