What if the underlying range is changed?

[hgl]

Should this spec codify if the range return by selection.getRangeAt(0) is changed, (e.g. insert a node into the range), the selection should change accordingly or not?

Currently, browsers behave differently on this one. Webkit and blink make selection to contain a new range. Gecko changes the selection. I personally think Gecko's behavior is the correct one.

[rniwa]

The spec matches WebKit/Blink behavior. See http://w3c.github.io/selection-api/#user-interactions where it says:

The user agent should allow the user to change the selection associated with the active document (defined in [HTML5]). If the user makes any modification to a selection, the user agent must create a new range with suitable start and end of the range ([DOM4]) and associate the selection with this new range (not modify the existing range), and set update selection's direction to forwards if the start is before or equal to the end, backwards if if the end is before the start, or directionless if the start and the end cannot be ordered due to the platform convention.

[rniwa]

Closing the issue as discussed on IRC. Please file a new issue should you find this solution unsatisfactory.