Bug 233654

Summary: AX: Keyboard focus not restored for back fragment navigations
Product: WebKit Reporter: Weston Thayer <me>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: andresg_22, cyb.ai.815, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: All   
OS: All   
Attachments:
Description Flags
Simple fragment demo page none

Weston Thayer
Reported 2021-11-30 12:23:56 PST
Created attachment 445453 [details] Simple fragment demo page Steps to reproduce: 1. Open focus-restoration.html 2. TAB to the "Section 3" link in the table of contents and press ENTER. Firefox navigates to the #sec3 fragment (added to history stack, page scrolls, sequential focus navigation starting point is at <h2 id="sec3">) 3. Go back with ALT/CMD + RIGHT_ARROW Actual results: Focus and sequential focus navigation starting point remains where it was after step (2). Expected results: As a user, I'd expect focus to be restored to <a href="#sec3">Section 3</a> so I could continue to navigate the table of contents with my keyboard. The spec (https://html.spec.whatwg.org/multipage/browsing-the-web.html#scroll-to-fragid) suggests that focus should move to <body> and sequential focus navigation starting point should be reset to the top of the document.
Attachments
Simple fragment demo page (3.14 KB, text/html)
2021-11-30 12:23 PST, Weston Thayer 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2021-11-30 12:24:24 PST
<rdar://problem/85880294>
Weston Thayer
Comment 3 2021-12-07 18:34:53 PST
Related https://github.com/whatwg/html/issues/7397
Note You need to log in before you can comment on or make changes to this bug.