[DevTools] Accessibility pane: Attempting to inspect root level a11y node leads to annoying weirdness |
|||
Issue descriptionWhen inspecting the root accessibility node, it attempts to inspect the Document node, which isn't visible in the DOM pane, so there is code to instead inspect the first child in the DOM. This causes a kind of "bounce" to happen and also typically inspects a node which is not part of the accessibility tree (such as a comment or doctype node), leading to more confusion. Instead, if a user attempts to inspect the root accessibility node, it should be a special case which leaves the root document node inspected but not visible in the DOM panel.
,
Jan 3 2017
New idea: special-case the root accessibility ("WebArea") node not to sync inspection with the DOM node.
,
Jan 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7caf9d35a14e3c4c093f2975df34d77b9dc035ed commit 7caf9d35a14e3c4c093f2975df34d77b9dc035ed Author: aboxhall <aboxhall@chromium.org> Date: Wed Jan 04 02:35:44 2017 Don't sync DOM selection for root a11y node BUG= 677885 Review-Url: https://codereview.chromium.org/2614553002 Cr-Commit-Position: refs/heads/master@{#441299} [modify] https://crrev.com/7caf9d35a14e3c4c093f2975df34d77b9dc035ed/third_party/WebKit/Source/devtools/front_end/accessibility/AXTreePane.js [modify] https://crrev.com/7caf9d35a14e3c4c093f2975df34d77b9dc035ed/third_party/WebKit/Source/devtools/front_end/accessibility/AccessibilitySidebarView.js
,
Jan 9 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by aboxhall@google.com
, Jan 3 20171.1 MB
1.1 MB View Download