New issue
Advanced search Search tips

Issue 823233 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

No spoken feedback on text input in Android window

Project Member Reported by yawano@chromium.org, Mar 19 2018

Issue description

Chrome Version: ToT
OS: Chrome

What steps will reproduce the problem?
(1) Enable spoken feedback.
(2) Open any Android window which has text input. Make sure that ChromeVox Arc native support is working for the window.
(3) Activate the input and type something.

What is the expected result?
Spoken feedback should be provided as user types text.

What happens instead?
No feedback.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 19 2018

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

commit a1608bb04f82615972d90c7b18926f8f6602761d
Author: David Tseng <dtseng@chromium.org>
Date: Mon Mar 19 16:14:31 2018

Revert "Reland: Better support crosh"

This reverts commit 2f8d70bbf03c37f4e64f7821c5c19f4ecdd66e84.

Reason for revert: breaks text input in ARC++
Bug:  823233 
Original change's description:
> Reland: Better support crosh
> 
> Rich editables should be skipped entirely (and not fall through to output).
> 
> Original change:
> - value change events often fire on richly editable text fields. We do not really use this in the state machine for rich text, so ignore it. It often causes poor state transitions e.g. speaking "deleted" in crosh when typing.
> - use the AutomationRichEditableText class in more cases. This acknowledges the usage in the wild where a page author can set role textbox on any node. When they do this it is assumed they manage a DOM selection unless they set the role on either an input or textarea where the browser does this on their behalf.
> 
> TBR=dmazzoni@chromium.org, dtseng@chromium.org
> 
> Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
> Change-Id: If555f157a7eeafe836929e9433891b2e7ae181df
> Reviewed-on: https://chromium-review.googlesource.com/953980
> Commit-Queue: David Tseng <dtseng@chromium.org>
> Reviewed-by: David Tseng <dtseng@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#541684}

TBR=dmazzoni@chromium.org,dtseng@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Change-Id: Ic585ad279e461b2b7144904180e3b1cb140e1588
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Reviewed-on: https://chromium-review.googlesource.com/968741
Reviewed-by: David Tseng <dtseng@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#544054}
[modify] https://crrev.com/a1608bb04f82615972d90c7b18926f8f6602761d/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
[modify] https://crrev.com/a1608bb04f82615972d90c7b18926f8f6602761d/chrome/browser/resources/chromeos/chromevox/cvox2/background/editing.js

Comment 2 by dtseng@chromium.org, Mar 19 2018

Status: fixed (was: Untriaged)

Sign in to add a comment