WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
307385
[MacOS] fast/events/onunload-not-on-body.html is a flaky text failure
https://bugs.webkit.org/show_bug.cgi?id=307385
Summary
[MacOS] fast/events/onunload-not-on-body.html is a flaky text failure
Diego De La Toba
Reported
2026-02-09 16:00:21 PST
fast/events/onunload-not-on-body.html is a flaky text failure across all architectures and styles. HISTORY:
https://results.webkit.org/?suite=layout-tests&test=fast%2Fevents%2Fonunload-not-on-body.html
TEXT DIFF: --- /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/fast/events/onunload-not-on-body-expected.txt +++ /Volumes/Data/worker/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/build/layout-test-results/fast/events/onunload-not-on-body-actual.txt @@ -1,3 +1,3 @@ -frame "<!--frame3-->" - has 1 onunload handler(s) +frame "<!--frame4-->" - has 1 onunload handler(s) CONSOLE MESSAGE: Use of window.alert is not allowed while unloading a page. you should only see one unload alert appear. DIFF URL:
https://build.webkit.org/results/Apple-Tahoe-Release-AppleSilicon-WK2-Tests/307099%40main%20(1543)/fast/events/onunload-not-on-body-pretty-diff.html
REPRODUCTION: I was able to reproduce this failure on macOS Tahoe ToT arm64 with the following: run-webkit-tests --force --release --no-retry --iterations 1000 fast/events/onunload-not-on-body.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
Comment 1
2026-02-09 16:00:28 PST
<
rdar://problem/170008549
>
Diego De La Toba
Comment 2
2026-02-09 16:06:40 PST
Pull request:
https://github.com/WebKit/WebKit/pull/58252
EWS
Comment 3
2026-02-09 16:08:40 PST
Test gardening commit
307119@main
(8275904a69cf): <
https://commits.webkit.org/307119@main
> Reviewed commits have been landed. Closing PR #58252 and removing active labels.
Diego De La Toba
Comment 4
2026-02-09 16:23:38 PST
Pull request:
https://github.com/WebKit/WebKit/pull/58254
Diego De La Toba
Comment 5
2026-02-09 16:24:59 PST
Looks like the test is flaky because it relies on an auto-generated frame identifier (frame3 or frame4) & this is causing the frame number to vary between runs. I’m going to push a patch that resolves this, please review (assuming this is NOT a webkit issue).
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug