Issue metadata
Sign in to add a comment
|
[Internal]: WebView contentEditable does not support ACTION_SET_TEXT |
||||||||||||||||||||||||
Issue descriptionInternal bug: https://b.corp.google.com/u/0/issues/113674363 Comment#0 : =========== Additional History: b/37641670, b/37641965 This will happen on any Android device that support Accessibility Acitons with any recent version of WebView. STEPS TO REPRODUCE: 1. Try to use AccessibilityNodeInfo.ACTION_SET_TEXT in the Gmail Compose message body. 2. Observe that the node does not support ACTION_SET_TEXT As an editable text field, I would expect the ability to set the text within the field. The field appears to accept single character input from the IME, but not being able to set the text is limiting in terms of A11y features. Things like undo or smart text replacement become difficult since the text cannot be set. The set of actions it appears to support are: [ACTION_CLEAR_FOCUS, ACTION_CLICK, ACTION_ACCESSIBILITY_FOCUS, ACTION_NEXT_AT_MOVEMENT_GRANULARITY, ACTION_PREVIOUS_AT_MOVEMENT_GRANULARITY, ACTION_NEXT_HTML_ELEMENT, ACTION_PREVIOUS_HTML_ELEMENT, ACTION_COPY, ACTION_PASTE, ACTION_CUT, ACTION_SET_SELECTION, ACTION_UNKNOWN] Previous fixes made Switch Access kind of work since input still comes from the IME, but lots of Switch Access's advanced text manipulation fails. Voice Access doesn't type via the IME which makes composing an email with it not possible through Gmail. Comment#1: ========== This should be the case for Chrome on Android too. WebView doesn't seem to do anything different, as far as I can see. This issue is raised as a feature request, hence marking as Untriaged for further inputs from dev team. Thanks!
,
Jan 8
,
Jan 15
I think this is actually an easy fix, assuming you only expect it to set plaintext. https://chromium-review.googlesource.com/c/chromium/src/+/1411292
,
Jan 16
(6 days ago)
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d9240658ffb6a5f156fd516ee478ced90e174349 commit d9240658ffb6a5f156fd516ee478ced90e174349 Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Wed Jan 16 09:26:26 2019 Implement accessible SetValue action for contenteditable Bug: 917817 Change-Id: Id1586493b47f74ca960fdf934fb099ec79225519 Reviewed-on: https://chromium-review.googlesource.com/c/1411292 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#623171} [modify] https://crrev.com/d9240658ffb6a5f156fd516ee478ced90e174349/content/browser/accessibility/accessibility_action_browsertest.cc [modify] https://crrev.com/d9240658ffb6a5f156fd516ee478ced90e174349/content/browser/accessibility/browser_accessibility_position.h [modify] https://crrev.com/d9240658ffb6a5f156fd516ee478ced90e174349/third_party/blink/renderer/modules/accessibility/ax_layout_object.cc
,
Jan 16
(6 days ago)
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Jan 8Status: Available (was: Untriaged)