chromium/src
0
Fork 0
Code Activity

Remove docs reference to dead class AXContentNodeData

Browse Source 
AXContentNodeData was folded into ui::AXNodeData in crrev.com/c/2270065.
Update a doc reference accordingly.

Change-Id: Ic05079b97501c0130244b0d0a5ca3ee744537da1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3116774
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dan Clark <daniec@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#914938}
This commit is contained in:
Dan Clark
2021-08-24 22:39:50 +00:00
committed by Chromium LUCI CQ
parent 6aff3e1a7a
commit 2256222e05
1 changed files with 8 additions and 9 deletions

17
docs/accessibility/overview.md

@ -462,14 +462,14 @@ events from Blink to the embedding content layer.
## The content layer
The content layer lives on both sides of the renderer/browser split. The content
layer translates WebAXObjects into [AXContentNodeData], which is a subclass of
[ui::AXNodeData]. The ui::AXNodeData class and related classes are Chromium's
cross-platform accessibility tree. The translation is implemented in
[BlinkAXTreeSource]. This translation happens on the renderer side, so the
ui::AXNodeData tree now needs to be sent to the browser, which is done by
calling the remote method [ax.mojom.RenderAccessibilityHost::HandleAXEvents()]
with the payload being serialized delta-updates to the tree, so that changes
that happen on the renderer side can be reflected on the browser side.
layer translates WebAXObjects into [ui::AXNodeData]. The ui::AXNodeData class
and related classes are Chromium's cross-platform accessibility tree. The
translation is implemented in [BlinkAXTreeSource]. This translation happens on
the renderer side, so the ui::AXNodeData tree now needs to be sent to the
browser, which is done by calling the remote method
[ax.mojom.RenderAccessibilityHost::HandleAXEvents()] with the payload being
serialized delta-updates to the tree, so that changes that happen on the
renderer side can be reflected on the browser side.
On the browser side, these IPCs are received by [RenderFrameHostImpl], and then
usually forwarded to [BrowserAccessibilityManager] which is responsible for:
@ -522,7 +522,6 @@ is defined by [automation.idl], which must be kept synchronized with
[ax.mojom.RenderAccessibilityHost::HandleAXEvents()]: https://source.chromium.org/chromium/chromium/src/+/main:content/common/render_accessibility.mojom;l=47
[ax.mojom.RenderAccessibility.PerformAction()]: https://source.chromium.org/chromium/chromium/src/+/main:content/common/render_accessibility.mojom;l=86
[AutomationInternalCustomBindings]: https://cs.chromium.org/chromium/src/extensions/renderer/api/automation/automation_internal_custom_bindings.h
[AXContentNodeData]: https://cs.chromium.org/chromium/src/content/common/ax_content_node_data.h
[AXLayoutObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_layout_object.h
[AXNodeObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_node_object.h
[AXObject]: https://cs.chromium.org/chromium/src/third_party/blink/renderer/modules/accessibility/ax_object.h