Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 8af8a7cdd78db735eaa75c88b9dd8b987512f697
https://github.com/WebKit/WebKit/commit/8af8a7cdd78db735eaa75c88b9dd8b987512f697
Author: Franco Vieira de Souza <[email protected]>
Date: 2026-01-24 (Sat, 24 Jan 2026)
Changed paths:
A
LayoutTests/performance-api/event-timing-entry-schedules-update-rendering-expected.txt
A
LayoutTests/performance-api/event-timing-entry-schedules-update-rendering.html
M LayoutTests/platform/ios/TestExpectations
M Source/WebCore/page/LocalDOMWindow.cpp
M Source/WebCore/page/LocalDOMWindow.h
M Source/WebCore/page/Page.cpp
M Source/WebCore/page/Page.h
M Source/WebCore/testing/Internals.cpp
M Source/WebCore/testing/Internals.h
M Source/WebCore/testing/Internals.idl
Log Message:
-----------
High INP (Interaction to Next Paint) for interactions with no immediate
screen updates
https://bugs.webkit.org/show_bug.cgi?id=305251
rdar://168016487
Reviewed by Ryan Reno
We now ensure "update the rendering" (Page::updateRendering()) is
scheduled to run whenever an event timing entry is queued to be
dispatched. This ensures the dispatch will happen in a timely manner.
Previously, static pages in which nothing forces an update to
rendering could take too long to dispatch the entries, producing
entries with unreasonably large durations. That could be interpreted
as the page being unresponsive in metrics such as INP.
In order to test this, we need to probe the scheduling state, so a new
testing API was added: window.internals.timeToNextRenderingUpdate().
Test added:
* LayoutTests/performance-api/event-timing-entry-schedules-update-rendering.html
Canonical link: https://commits.webkit.org/306142@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
