New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix web_test pointerevent_coordinates_when_locked on wpt #16265
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already reviewed downstream.
The test was failing on WPT[1] because test driver only takes integer coordinates, but the test was using getBoundingClientRect which returns float values. This CL changes the test to set the "origin" for test driver actions so that there is no need to use getBoundingClientRect. [1] https://wpt.fyi/results/pointerevents/pointerlock/pointerevent_coordinates_when_locked.html Change-Id: I56b2c052805b3bc174573564d176d6660accd7cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553645 Reviewed-by: Lan Wei <lanwei@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#647877}
fd0cb60
to
8ea9611
Compare
Following tests failed at Firefox Nightly /pointerevents/pointerlock/pointerevent_coordinates_when_locked.html
Unstable results
::: Running tests in a loop 10 times : FAIL |
Note: Already contacted the author |
@KyleJu is there a tracking bug? I don't see any follow-up commits to this test in Chromium. |
Oops sorry missed it. Let me address it now |
This PR fixed a syntax error on pointerlock test that was previously failing [https://wpt.fyi/results/?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned&q=pointerevents%2Fpointerlock%2Fpointerevent_coordinates_when_locked]. Doesn't introduce any new flakiness. Admin merge @Hexcles ? |
The test was failing on WPT[1] because test driver only takes integer
coordinates, but the test was using getBoundingClientRect which
returns float values.
This CL changes the test to set the "origin" for test driver actions
so that there is no need to use getBoundingClientRect.
[1] https://wpt.fyi/results/pointerevents/pointerlock/pointerevent_coordinates_when_locked.html
Change-Id: I56b2c052805b3bc174573564d176d6660accd7cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553645
Reviewed-by: Lan Wei <lanwei@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#647877}