Define what should return getTargetRanges() of beforeinput after propagation
#114
Comments
moz-wptsync-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this issue
Aug 4, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1655393 gecko-commit: 12f21ad909371384939bb38d65cf1dbc797b5bf9 gecko-integration-branch: autoland gecko-reviewers: smaug
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this issue
Aug 4, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527
moz-wptsync-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this issue
Aug 4, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1655393 gecko-commit: 12f21ad909371384939bb38d65cf1dbc797b5bf9 gecko-integration-branch: autoland gecko-reviewers: smaug
xeonchen
pushed a commit
to xeonchen/gecko
that referenced
this issue
Aug 4, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this issue
Aug 6, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527 UltraBlame original commit: 12f21ad909371384939bb38d65cf1dbc797b5bf9
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this issue
Aug 6, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527 UltraBlame original commit: 12f21ad909371384939bb38d65cf1dbc797b5bf9
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this issue
Aug 6, 2020
There are no automated tests for `InputEvent.getTargetRanges()` because it is set only when `beforeinput` event, but it's defined as not dispatched by `document.execCommand`. However, we can synthesize `beforeinput` event with test driver. On the other hand, the definition in Input Events spec is not clear. Therefore, most of the tests won't be passed on any browsers for now. There are some spec issues which I filed: * w3c/input-events#112 * w3c/input-events#113 * w3c/input-events#114 These new test must be useful when browser vendors discuss the issues. Differential Revision: https://phabricator.services.mozilla.com/D85527 UltraBlame original commit: 12f21ad909371384939bb38d65cf1dbc797b5bf9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I realize that Chrome returns
nullfromgetTargetRanges()ofbeforeinputevent after its propagation finished. But in untrusted events, it's initialized with the dictionary and returns same value even the ranges become invalid due to DOM mutation. So, I was thinking that it should keep returning same value which is created by browser's editor before dispatching thebeforeinputevent.The text was updated successfully, but these errors were encountered: