0

Android docs, follow-up CL to address typos etc.

This is a follow-up CL to crrev.com/c/3504190 , which added a large
amount of documentation for Android accessibility. This CL is meant to
fix typos, formatting, confusing wording, etc.

AX-Relnotes: N/A
Bug: N/A
Change-Id: I3e4c162c9483362e9dafa4ed4fc7e35c3f5dd230
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3508331
Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Mark Schillaci <mschillaci@google.com>
Cr-Commit-Position: refs/heads/main@{#978489}
This commit is contained in:
Mark Schillaci
2022-03-07 22:53:49 +00:00
committed by Chromium LUCI CQ
parent 39da42b29b
commit 03ce1bb50f

@ -731,15 +731,15 @@ Piece of cake!
The way touch exploration works on Android is complicated. The process that happens
during any hover event is:
* User begins dragging their finger
* Java-side View receives a hover event and passes this through to C++
* Accessibility code sends a hit test action to the renderer process
* The renderer process fires a HOVER accessibility event on the accessibility
node at that coordinate
* [WebContentsAccessibilityImpl#handleHover](https://source.chromium.org/chromium/chromium/src/+/main:content/public/android/java/src/org/chromium/content/browser/accessibility/WebContentsAccessibilityImpl.java?q=%22private%20void%20handleHover%22) is called for that node.
* We fire a TYPE\_VIEW\_HOVER\_ENTER AccessibilityEvent on that node.
* We fire a TYPE\_VIEW\_HOVER\_EXIT AccessibilityEvent on the previous node.
* TalkBack sets accessibility focus to the targeted node.
1. User begins dragging their finger
2. Java-side View receives a hover event and passes this through to C++
3. Accessibility code sends a hit test action to the renderer process
4. The renderer process fires a HOVER accessibility event on the accessibility
node at that coordinate
5. [WebContentsAccessibilityImpl#handleHover](https://source.chromium.org/chromium/chromium/src/+/main:content/public/android/java/src/org/chromium/content/browser/accessibility/WebContentsAccessibilityImpl.java?q=%22private%20void%20handleHover%22) is called for that node.
6. We fire a TYPE\_VIEW\_HOVER\_ENTER AccessibilityEvent on that node.
7. We fire a TYPE\_VIEW\_HOVER\_EXIT AccessibilityEvent on the previous node.
8. TalkBack sets accessibility focus to the targeted node.
- WebView and Custom Tabs