1668133 - Split off the check of InputEvent.getTargetRanges() result after `beforeinput` event propagation in WPT

Status: RESOLVED FIXED

(Core :: DOM: Events, task, P2)

Description

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(away: 6/25-6/28)]

Currently, the WPTs for InputEvent.getTargetRanges() check its result after propagation, but Chrome always fail it so that it's hard to check which tests indicates actual different behavior with Gecko. Therefore, it's better to check it in a separated test.

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(away: 6/25-6/28)]

Attachment: Bug 1668133 - Check consistency of `getTargetRanges()` at calling various timing in an independent WPT r=smaug!

Currently, it's tested in input-events-get-target-ranges-*.tentative.html
after checking the target ranges, however, Blink always fails this check.
That makes it harder to check which test actually failed on Chrome.

Therefore, this patch makes the existing tests stop check it, and creates
new WPT to check only it.

Note that due to some prettier's rlues have been changed so that VSCode
reformatted the JS file.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/bd5d3910d2a4
Check consistency of `getTargetRanges()` at calling various timing in an independent WPT r=smaug

Comment 3

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/25942 for changes under testing/web-platform/tests

Comment 4

[Andreea Pavel [:apavel]]

https://hg.mozilla.org/mozilla-central/rev/bd5d3910d2a4

Comment 5

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by jgraham