[Webkit-unassigned] [Bug 281642] New: AX: AXIsolatedTree::{collectNodeChangesForSubtree, removeSubtreeFromNodeMap} modify m_nodeMap children IDs when they shouldn't
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Oct 16 19:30:56 PDT 2024
https://bugs.webkit.org/show_bug.cgi?id=281642
Bug ID: 281642
Summary: AX: AXIsolatedTree::{collectNodeChangesForSubtree,
removeSubtreeFromNodeMap} modify m_nodeMap children
IDs when they shouldn't
Product: WebKit
Version: Safari 18
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Accessibility
Assignee: webkit-unassigned at lists.webkit.org
Reporter: tyler_w at apple.com
CC: andresg_22 at apple.com,
webkit-bug-importer at group.apple.com
A key component of AXIsolatedTree::updateChildren is comparing the "old" children (what is in the node map) for an object vs. it's new children (the result of AccessibilityObject::children()). This makes AXIsolatedTree::{collectNodeChangesForSubtree, removeSubtreeFromNodeMap}'s behavior of modifying the children IDs for existing entries in the node map problematic, as that can happen before we've had a chance to call `updateChildren`, thus making the old and new children "match" even though they have actually changed since we last ran `updateChildren`. This means we won't create a new node change for this object, resulting in stale properties and missing children.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241017/e8dbb6b2/attachment.htm>
More information about the webkit-unassigned
mailing list