Use the correct BrowserAccessibilityManager for a node
No change in behavior expected, but this is to fix an inconsistency in the code where calls were made using a mismatched BrowserAccessibility and BrowserAccessibilityManager. Bug: None Change-Id: I73cac6b0e901c2685272415fcb28c7542ed6fe34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615201Reviewed-by:Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#841554}
Showing
Please register or sign in to comment