getTargetRanges definition for EditContext is unclear

[ltenmoz]

#174 updated the definition of getTargetRanges for EditContext

getTargetRanges() returns an array of StaticRanges representing the content that the event will modify if it is not canceled, if the editing host is contenteditable node or an EditContext editing host

but this doesn't really make sense: the browser does not modify the DOM from user input for EditContext (that is up to the web author to do). So perhaps for EditContext it should say something like "getTargetRanges() returns the array of StaticRanges that would be modified if the EditContext editing host were instead contenteditable" (a bit awkward, but I'm not sure if there's a better way of wording it)

[johanneswilm]

but this doesn't really make sense: the browser does not modify the DOM from user input for EditContext (that is up to the web author to do).

I agree. Maybe use another formulation such as:

"getTargetRanges() returns an array of StaticRanges representing the content that the event will modify if it is not canceled, if the editing host is contenteditable node, or the content that the browser assumes to be affected by the change in case of an EditContext editing host"

Still sounds a bit awkward, but that is effectively what we mean, right?

"getTargetRanges() returns the array of StaticRanges that would be modified if the EditContext editing host were instead contenteditable"

The problem with that I see is that we will make EditContext effectively depend on contenteditable - which it may replace some day. It also means that if we add new editing features to EditContext (multiple ranges, etc.), we also need to add them to contenteditable.

[ltenmoz]

Sure, sounds good :) I've filed a PR here: #179

[dandclark]

Change sounds reasonable to me. Thanks for fixing this.