Issue metadata
Sign in to add a comment
|
Opening dev tools is slow when accessibility is enabled |
||||||||||||||||||||||
Issue descriptionOS: 10.12 beta Chrome: 55.0.2846.0 debug build 1) Open a tab and leave it at the new tab page 2) Enable VoiceOver (command-f5) 3) Open developer tools The browser goes completely unresponsive for over a minute. *Eventually*, it finishes updating the dev tools pane, so it's not hung, just working very very slowly.
,
Sep 1 2016
If a release build is a bit slower with VoiceOver on but still usable, then this is working as intended and probably not a recent regression.
,
Sep 1 2016
Also: SerializeChanges is expected if accessibility is slow; that's what triggers most of the work. I'd be curious what the top function is once you get inside Blink - something in one of the AXObject subclasses, so the top function matching AXObject::, AXNodeObject::, or AXLayoutObject::
,
Sep 1 2016
We need to fix it, we are getting requests like this too often.
,
Sep 1 2016
Pavel, are you able to point to any other bugs filed about this to help diagnose?
,
Nov 15 2016
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 10 2017
Closing this since we have other bugs tracking performance, and debug mode is not expected to be fast. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ellyjo...@chromium.org
, Sep 1 2016