Add `InputEvent.getTargetRanges()` WPT with driver
Categories
(Core :: DOM: Events, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox81 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
There is only one manual test of InputEvent.getTargetRanges(). Of course, this is not enough, and in edge cases, other browsers return wrong ranges (e.g., when deleting invisible white-spaces automatically). So, I think that we should create testcases which synthesizes Delete and Backspace with various modifiers, and check whether getTargetRanges() and actually removed range is exactly same or not.
|
||
Updated•4 years ago
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
|
Assignee | |
Comment 1•4 years ago
|
||
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:
- https://github.com/w3c/input-events/issues/112
- https://github.com/w3c/input-events/issues/113
- https://github.com/w3c/input-events/issues/114
These new test must be useful when browser vendors discuss the issues.
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Description
•