New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 819669 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Team-Accessibility

Blocking:
issue 801086



Sign in to add a comment

Clicking on a WebView text field using an Android accessibility service doesn't focus it

Project Member Reported by dmazz...@chromium.org, Mar 7 2018

Issue description

Here's one repro:

1. Enable Switch Access. By default it should be configured so that Volume Down highlights the next item on the screen and Volume Up selects. Ensure this is working, for example in Settings or in the Home Screen.
2. Open Gmail
3. Select Compose
4. Use Volume Down to move to the Subject text field and press Volume Up to Select. It gets focused.
5. Now use Volume Down to move to the body (Compose Email) text field and press Volume Up to Select.

Expected: the field should focus and the virtual keyboard should pop up if it wasn't already.

Actual: the field does not focus

This can also be reproduced with Voice Access, see b/37641670 - but that product might not be available to everyone.

You can reproduce this with almost any app that has a text field in a WebView. The problem happens when focus is initially not in the WebView at all, and then you try to click in a text field in the WebView. If focus is already somewhere else in the WebView, focusing the text field succeeds.

 
Blocking: 801086
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 8 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/294b262a66745601a705d9df039741737c425f42

commit 294b262a66745601a705d9df039741737c425f42
Author: Dominic Mazzoni <dmazzoni@chromium.org>
Date: Thu Mar 08 07:18:21 2018

Ensure WebView is focused when handling an accessibility action.

When an Android accessibility service sends us a CLICK or FOCUS action
on a specific node in a WebView, we should first focus the WebView itself.
Otherwise clicking on a text field using an accessibility service doesn't
actually move input focus there and pop up the virtual keyboard.

Bug:  819669 
Change-Id: I8e4069324e45516fbc1621723885ad8448fdc862
Reviewed-on: https://chromium-review.googlesource.com/953322
Reviewed-by: Paul Miller <paulmiller@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541748}
[modify] https://crrev.com/294b262a66745601a705d9df039741737c425f42/content/public/android/java/src/org/chromium/content/browser/accessibility/WebContentsAccessibilityImpl.java

Status: Fixed (was: Assigned)

Sign in to add a comment