Issue metadata
Sign in to add a comment
|
Enabling ChromeVox sends 4 copies of the AX node tree to the extension |
||||||||||||||||||||
Issue descriptionToT f531aaf8e629237000c645f6046ea2be0857ed66 linux-chromeos Patch in https://chromium-review.googlesource.com/c/chromium/src/+/1185858 which adds some logging. * Turn off ChromeVox * Restart Chrome * Ensure 1 browser window is open * Turn on ChromeVox AutomationManagerAura::Enable() is called 4 times, from AutomationInternalEnableDesktopFunction::Run(). Each calls serializes the entire desktop node tree and sends it to the extension. This seems inefficient to me. (I noticed this while debugging a problem with the keyboard shortcut viewer app, which has an early-exit for automation being enabled multiple times. My early-exit sometimes breaks ChromeVox, which seems to rely on this multiple-enable behavior.)
,
Aug 23
Every call to AutomationManagerAura::Enable() deletes the serializer, despite the boolean parameter to Reset() that says not to reset it. https://cs.chromium.org/chromium/src/chrome/browser/ui/aura/accessibility/automation_manager_aura.cc?q=automation_manager_aura.cc&sq=package:chromium&l=88 https://cs.chromium.org/chromium/src/chrome/browser/ui/aura/accessibility/automation_manager_aura.cc?sq=package:chromium&g=0&l=180 Logging in AutomationInternalCustomBindings::OnAccessibilityEvents shows 4 copies of AXEventloadComplete when I turn on ChromeVox with no browser windows open.
,
Sep 14
,
Sep 14
,
Sep 20
,
Jan 16
Bumping up to P2. I'm still seeing this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Aug 23