Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 487ec443bd23024a0677533a9991380a55c3f64b
https://github.com/WebKit/WebKit/commit/487ec443bd23024a0677533a9991380a55c3f64b
Author: Aditya Keerthi <[email protected]>
Date: 2026-03-10 (Tue, 10 Mar 2026)
Changed paths:
A
LayoutTests/imported/w3c/web-platform-tests/html/interaction/focus/sequential-focus-navigation-after-disabled-expected.txt
A
LayoutTests/imported/w3c/web-platform-tests/html/interaction/focus/sequential-focus-navigation-after-disabled.html
M LayoutTests/platform/ios/TestExpectations
M Source/WebCore/page/Page.cpp
Log Message:
-----------
REGRESSION (260067@main): Tabbing position lost when button is disabled
https://bugs.webkit.org/show_bug.cgi?id=309544
rdar://120676409
Reviewed by Ryosuke Niwa and Abrar Rahman Protyasha.
260067@main implemented the focus fixup rule to clear focus from an element
that is no longer focusable (e.g. a button that became disabled). This change
also had the effect of resetting the sequential focus navigation starting point.
Consequently, the next Tab key press started focus navigation from the
beginning of the document instead of advancing from where the disabled element
was.
Fix by preserving the sequential focus navigation starting point by resetting
it to the now-unfocusable element after clearing focus, the same way the
element-removal code path already does.
*
LayoutTests/imported/w3c/web-platform-tests/html/interaction/focus/sequential-focus-navigation-after-disabled-expected.txt:
Added.
*
LayoutTests/imported/w3c/web-platform-tests/html/interaction/focus/sequential-focus-navigation-after-disabled.html:
Added.
* LayoutTests/platform/ios/TestExpectations:
* Source/WebCore/page/Page.cpp:
(WebCore::Page::updateRendering):
Canonical link: https://commits.webkit.org/308991@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
