Bug 310217 – [macOS] imported/w3c/web-platform-tests/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element.html is a flaky text failure

• Component: UI Events
• Status: NEW

[Diego De La Toba]

imported/w3c/web-platform-tests/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element.html is a flaky text failure on macOS. 

HISTORY:
https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fpointerevents%2Fpointerevent_pointer_boundary_events_after_removing_last_over_element.html

Note: While results db shows this only failing on debug this test also fails on release when testing locally. 

TEXT DIFF:
--- /Volumes/Data/worker/Apple-Tahoe-Debug-AppleSilicon-WK2-Tests/build/layout-test-results/imported/w3c/web-platform-tests/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element-expected.txt
+++ /Volumes/Data/worker/Apple-Tahoe-Debug-AppleSilicon-WK2-Tests/build/layout-test-results/imported/w3c/web-platform-tests/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element-actual.txt
@@ -1,4 +1,4 @@
 
 FAIL After removing the last over element, redundant pointerenter events should not be fired on the ancestors assert_equals: expected "pointerover@div#parent, pointerout@div#parent, pointerleave@div#parent, pointerleave@div#grandparent, pointerover@body, pointermove@body" but got "pointerover@body, pointermove@body"
-FAIL After removing the root element in the shadow under the cursor, pointerleave events should be targeted outside the shadow, but redundant pointerenter events should not be fired assert_equals: expected "pointerover@div#shadowHost, pointerout@div#shadowHost, pointerleave@div#shadowHost, pointerleave@div#containerOfShadowHost, pointerover@body, pointermove@body" but got "pointerover@body, pointermove@body"
+PASS After removing the root element in the shadow under the cursor, pointerleave events should be targeted outside the shadow, but redundant pointerenter events should not be fired
 

DIFF URL:
https://build.webkit.org/results/Apple-Tahoe-Debug-AppleSilicon-WK2-Tests/309478@main%20(1348)/imported/w3c/web-platform-tests/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element-pretty-diff.html


REPRODUCTION:
run-webkit-tests --no-build --no-retry --no-show-results --exit-after-n-failures=1 --expect-pass --iterations=24 --force -f --debug imported/w3c/web-platform-tests/pointerevents/pointerevent_pointer_boundary_events_after_removing_last_over_element.html

Marking expectations as pass fail while this pends investigation.

[Radar WebKit Bug Importer]

<rdar://problem/172861599>

[Diego De La Toba]

Test gardening pull request: https://github.com/WebKit/WebKit/pull/60888

[EWS]

Test gardening commit 309504@main (8b13f83ea9ad): <https://commits.webkit.org/309504@main>

Reviewed commits have been landed. Closing PR #60888 and removing active labels.

[Diego De La Toba]

This test currently has expectations marked as FAIL for both subtests, however, these tests flakily assert PASS. Adding a 250ms pause after pointer movements results in constant PASS. Putting this up as a PR.

[Abrar Rahman Protyasha]

Flaky PASS is a good problem to have 😃

[Abrar Rahman Protyasha]

I would prefer to not hardcode a 250ms delay.

[Diego De La Toba]

Pull request: https://github.com/WebKit/WebKit/pull/60901

[Diego De La Toba]

(In reply to Abrar Rahman Protyasha from comment #5)
> Flaky PASS is a good problem to have 😃

It certainly is! I definitely think it’s possible to get this test to a point where it’s consistently passing with the right timing adjustments.