Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: db63ddf0702c0d89f925e983ad07d7b90a69f7a7
https://github.com/WebKit/WebKit/commit/db63ddf0702c0d89f925e983ad07d7b90a69f7a7
Author: Ryosuke Niwa <[email protected]>
Date: 2026-04-23 (Thu, 23 Apr 2026)
Changed paths:
M
LayoutTests/http/tests/frame-throttling/raf-throttle-in-cross-origin-subframe-expected.txt
M
LayoutTests/http/tests/frame-throttling/raf-throttle-in-cross-origin-subframe.html
M LayoutTests/platform/mac/TestExpectations
Log Message:
-----------
http/tests/frame-throttling/raf-throttle-in-cross-origin-subframe.html is
flaky
https://bugs.webkit.org/show_bug.cgi?id=313132
rdar://168818015
Reviewed by Simon Fraser.
The test was consistently failing now because of the stale enum name:
NonInteractiveCrossOriginFrame.
Fixed it by updating it to use NonInteractedCrossOriginFrame instead to match
the source in AnimationFrameRate.h.
The flakiness was caused by non-deterministic ordering between script
executions in two iframes.
Replaced the fire-both-and-wait-for-two pattern with a sequential
queryThrottleState helper that uses a per-query
addEventListener, posts to one frame at a time, and awaits the response before
proceeding to the next.
The window.onmessage handler now only handles frameload messages. This
guarantees cross-origin is always queried
and logged before same-origin.
*
LayoutTests/http/tests/frame-throttling/raf-throttle-in-cross-origin-subframe-expected.txt:
*
LayoutTests/http/tests/frame-throttling/raf-throttle-in-cross-origin-subframe.html:
* LayoutTests/platform/mac/TestExpectations:
Canonical link: https://commits.webkit.org/311875@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
