Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 26cd9a54b08c738f6b2161df7639bde75181f8bd
https://github.com/WebKit/WebKit/commit/26cd9a54b08c738f6b2161df7639bde75181f8bd
Author: Simon Fraser <[email protected]>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M Source/WebCore/page/Quirks.cpp
M Source/WebCore/page/Quirks.h
M Source/WebCore/page/QuirksData.h
M Source/WebCore/page/scrolling/AsyncScrollingCoordinator.cpp
Log Message:
-----------
REGRESSION (308320@main): x.com jumps to the wrong scroll offset when
navigating back from a thread
https://bugs.webkit.org/show_bug.cgi?id=314151
rdar://175565114
Reviewed by Brent Fulgham.
When navigating back from a thread, x.com does a programmatic scroll to restore
the
scroll position in the main feed. But it does this before the main feed has
been fully
loaded (recall that `scrollTo` does a layout, so we know that layout is up to
date),
so it's scrolling to a large y offset that is larger than the current scroll
max.
The clamping added in 308320@main now clamps, breaking this behavior, so add a
quirk
for x.com to restore the old behavior.
* Source/WebCore/page/Quirks.cpp:
* Source/WebCore/page/Quirks.h:
* Source/WebCore/page/QuirksData.h:
* Source/WebCore/page/scrolling/AsyncScrollingCoordinator.cpp:
(WebCore::AsyncScrollingCoordinator::requestScrollToPosition):
Canonical link: https://commits.webkit.org/312749@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
