Bug 260174

Summary: AX: Fix multiple-label-input test in ITM mode
Product: WebKit Reporter: Joshua Hoffman <jhoffman23>
Component: AccessibilityAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: aboxhall, andresg_22, apinheiro, cfleizach, dmazzoni, ews-watchlist, jcraig, jdiggs, samuel_white, tyler_w, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Joshua Hoffman
Reported 2023-08-14 14:18:00 PDT
The accessibility/multiple-label-input test times out in isolated tree mode when using innerText.
Attachments
Patch (5.59 KB, patch)
2023-08-14 14:55 PDT, Joshua Hoffman
no flags
Patch (6.45 KB, patch)
2023-08-14 20:33 PDT, Joshua Hoffman
no flags
Radar WebKit Bug Importer
Comment 1 2023-08-14 14:18:11 PDT
Joshua Hoffman
Comment 2 2023-08-14 14:55:48 PDT
Tyler Wilcock
Comment 3 2023-08-14 16:38:53 PDT
Comment on attachment 467272 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=467272&action=review > Source/WebCore/accessibility/AXObjectCache.cpp:4091 > + if (auto* axParent = notification.first->parentObject()) { > + if (axParent->isLabel() && axParent->correspondingControlForLabelElement()) > + updateNode(axParent->correspondingControlForLabelElement()); Let's use a RefPtr to protect usage of `axParent`, since we call axParent->correspondingControlForLabelElement() which does non-trivial work that could potentially destroy it. We can also use C++17-style multi-condition if-statements to make this more concise: if (RefPtr axParent = notification.first->parentObject(); axParent && axParent->isLabel()) { if (RefPtr correspondingControl = axParent->correspondingControlForLabelElement()) updateNode(axParent->correspondingControl.get()); } break; > Source/WebCore/accessibility/isolatedtree/AXIsolatedTree.cpp:615 > + if (axObject.isLabel() && axObject.correspondingControlForLabelElement()) > + updateNode(*axObject.correspondingControlForLabelElement()); correspondingControlForLabelElement does a bit of work, so let's only call it once. Something like this might work: if (RefPtr correspondingControl = axObject.isLabel() ? axObject.correspondingControlForLabelElement() : nullptr) updateNode(*correspondingControl);
Joshua Hoffman
Comment 4 2023-08-14 20:33:35 PDT
Andres Gonzalez
Comment 5 2023-08-15 08:18:18 PDT
(In reply to Joshua Hoffman from comment #4) > Created attachment 467276 [details] > Patch --- a/Source/WebCore/accessibility/AXObjectCache.cpp +++ b/Source/WebCore/accessibility/AXObjectCache.cpp + case AXTextChanged: + updateNode(notification.first); + if (RefPtr axParent = notification.first->parentObject(); axParent && axParent->isLabel()) { + if (RefPtr correspondingControl = axParent->correspondingControlForLabelElement()) + updateNode(correspondingControl.get()); + } + break; The update of the related nodes and properties should happen in AXIsolatedTree::updateNode. So I would leave this as before and move this additional logic to AXIsolatedTree. --- a/Source/WebCore/accessibility/isolatedtree/AXIsolatedTree.cpp +++ b/Source/WebCore/accessibility/isolatedtree/AXIsolatedTree.cpp + if (RefPtr correspondingControl = axObject.isLabel() ? axObject.correspondingControlForLabelElement() : nullptr) + updateNode(*correspondingControl); I see that you are already doing part of it in in here, so do the whole thing here.
Joshua Hoffman
Comment 6 2023-08-15 10:36:24 PDT
(In reply to Andres Gonzalez from comment #5) > (In reply to Joshua Hoffman from comment #4) > > Created attachment 467276 [details] > > Patch > > > The update of the related nodes and properties should happen in > AXIsolatedTree::updateNode. So I would leave this as before and move this > additional logic to AXIsolatedTree. We want to do this update when AXTextChanged, but AXIsolatedTree::updateNode doesn't know which notification was sent—so this allows us to conditionally do the update.
EWS
Comment 7 2023-08-15 11:00:30 PDT
Committed 266919@main (28bfc960f4a1): <https://commits.webkit.org/266919@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 467276 [details].
Note You need to log in before you can comment on or make changes to this bug.