RESOLVED FIXED301760
AX: focused node should be nullptr when a different frame has focus 
https://bugs.webkit.org/show_bug.cgi?id=301760
Summary AX: focused node should be nullptr when a different frame has focus
Dominic Mazzoni
Reported 2025-10-31 08:55:20 PDT
This applies when the ENABLE_ACCESSIBILITY_LOCAL_FRAME flag is enabled, in preparation for site isolation. Previously, there was one AXObjectCache for the whole page, and the current focused element always returned the focused element from any frame. If there was no focused element, the root was returned. With this flag enabled (required for site isolation), there's one AXObjectCache for each frame. When determining the focused node across all frames in the current process, each frame is now keeping track of focus separately - that means that frames that are not currently focused must return nullptr as their own focused node.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2025-10-31 08:55:25 PDT
<rdar://problem/163797834>
Dominic Mazzoni
Comment 2 2025-10-31 08:59:07 PDT
Pull request: https://github.com/WebKit/WebKit/pull/53260
EWS
Comment 3 2025-11-03 14:31:38 PST
Committed 302501@main (ee35cc63fdab): <https://commits.webkit.org/302501@main> Reviewed commits have been landed. Closing PR #53260 and removing active labels.
Note You need to log in before you can comment on or make changes to this bug.