Bug 314136
| Summary: | [macOS] accessibility/mac/client/div-bounds.html is a flaky text failure. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Diego De La Toba <d_delatoba> |
| Component: | New Bugs | Assignee: | Diego De La Toba <d_delatoba> |
| Status: | NEW | ||
| Severity: | Normal | CC: | dm_mazzoni, webkit-bot-watchers-bugzilla, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Diego De La Toba
accessibility/mac/client/div-bounds.html is a flaky text failure on macOS.
HISTORY:
https://results.webkit.org/?suite=layout-tests&test=accessibility%2Fmac%2Fclient%2Fdiv-bounds.html
DIFF:
--- /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/accessibility/mac/client/div-bounds-expected.txt
+++ /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/accessibility/mac/client/div-bounds-actual.txt
@@ -8,8 +8,8 @@
div1 height: 80
div2 width: 120
div2 height: 60
-x difference (div2.x - div1.x): 50
-y difference (div2.y - div1.y): 130
+x difference (div2.x - div1.x): 0
+y difference (div2.y - div1.y): 0
PASS successfullyParsed is true
DIFF URL:
https://build.webkit.org/results/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/312628@main%20(3676)/accessibility/mac/client/div-bounds-pretty-diff.html
REPRODUCTION:
I was able to reproduce the failure on macOS 26.4 release ToT with the following:
run-webkit-tests --no-build --no-retry --no-show-results --exit-after-n-failures=1 --expect-pass --iterations=10 --force -f --release accessibility/mac/client/div-bounds.html
I am going to mark expectations as pass fail while this pends investigation.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/176309594>
Diego De La Toba
Test gardening pull request: https://github.com/WebKit/WebKit/pull/64309
EWS
Test gardening commit 312650@main (af655535c03c): <https://commits.webkit.org/312650@main>
Reviewed commits have been landed. Closing PR #64309 and removing active labels.
Diego De La Toba
I think what's happening here is a timing issue where the test grabs element positions before they settle. I resolved locally by adding a 'waitFor' poll that waits until elements are in the right position.
Diego De La Toba
Pull request: https://github.com/WebKit/WebKit/pull/64313
Diego De La Toba
This appears to be a genuine bug since isFrameGeometryInitialized and waitForFrameGeometryReady are supposed to guarantee it is safe to query geometry.