Issue metadata
Sign in to add a comment
|
[Talkback] Contenteditable not identified as editable text
Reported by
r9852508...@gmail.com,
May 26 2016
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Enable Talkback 2. Launch activity and tap on webview which contains "contenteditable" tag What is the expected behavior? Speak "edit text" or "start to edit" if content is editable What went wrong? Only speak content Did this work before? No Chrome version: 51.0.2704.61 Channel: n/a OS Version: 6.0. Flash Version: It can reproduce on nexus 5 (6.0.1)
,
Jun 3 2016
Not sure this is a feature or a bug. I bet chrome has the same behavior. Assigning to dmazzoni@chromium.org
,
Nov 15 2016
,
Nov 15 2016
,
Nov 15 2016
,
Nov 17 2016
Just verified, Chrome behaves the same way. So, removing from WebView queue. (I also don't recall this ever working as the reporter expects...not sure if it's intended or not.)
,
Mar 6 2017
,
Mar 27 2017
,
Apr 21 2017
,
Apr 21 2017
,
Aug 7 2017
,
Aug 7 2017
This is still very much reproducible with the latest builds of Canary. Even though the keyboard does come up, when the field is tapped on, Talkback user has no way to differentiate the contenteditable area from the text surrounding it.
,
Aug 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 28
This test shows that we're not exposing the right role for Android contentediables: https://cs.chromium.org/chromium/src/content/test/data/accessibility/html/contenteditable-descendants-expected-android.txt
,
Dec 7
,
Dec 8
dmazzoni@ - is this supposed to have the UI>Browser component? It seems like an issue interacting with web contents.
,
Dec 10
Removing other components
,
Dec 21
In progress: https://chromium-review.googlesource.com/c/chromium/src/+/1388387 https://chromium-review.googlesource.com/c/chromium/src/+/1388388
,
Dec 24
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8ce6de372855256486dc7feb8bf68a73291d293d commit 8ce6de372855256486dc7feb8bf68a73291d293d Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Mon Dec 24 08:28:19 2018 Contenteditable should have EditText class name On some platforms, a simple text field, and a contenteditable region of the page are handled differently, so we don't explicitly have a role for the root of a contenteditable region. On Android, TalkBack won't recognize it as a text field if it doesn't have the correct class name, so set the class name appropriately for contenteditable too so that Android will treat it as a text field. Bug: 614907 Change-Id: Ib923452a17604a3dd0a79030ae1fec64dd71f995 Reviewed-on: https://chromium-review.googlesource.com/c/1388387 Reviewed-by: Paul Miller <paulmiller@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#618812} [modify] https://crrev.com/8ce6de372855256486dc7feb8bf68a73291d293d/content/browser/accessibility/browser_accessibility_android.cc [modify] https://crrev.com/8ce6de372855256486dc7feb8bf68a73291d293d/content/public/android/javatests/src/org/chromium/content/browser/accessibility/WebContentsAccessibilityTest.java [modify] https://crrev.com/8ce6de372855256486dc7feb8bf68a73291d293d/content/test/data/accessibility/aria/aria-readonly-expected-android.txt [modify] https://crrev.com/8ce6de372855256486dc7feb8bf68a73291d293d/content/test/data/accessibility/html/contenteditable-with-no-descendants-expected-android.txt
,
Jan 11
This issue has been marked as started, but has no owner. Making available.
,
Jan 16
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bfb4db2020de72fcfe32e5842cedabc9c7eb8613 commit bfb4db2020de72fcfe32e5842cedabc9c7eb8613 Author: Dominic Mazzoni <dmazzoni@chromium.org> Date: Wed Jan 16 01:52:41 2019 Focus contenteditable on DoDefault, to match input and textarea On Android there was no good way to focus a contenteditable with TalkBack as the main double-tap gesture was calling DoDefault. Bug: 614907 Change-Id: I9c6a975a9b9e35cd3c618c199418908d1c5269f3 Reviewed-on: https://chromium-review.googlesource.com/c/1388388 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: Alice Boxhall <aboxhall@chromium.org> Cr-Commit-Position: refs/heads/master@{#623007} [modify] https://crrev.com/bfb4db2020de72fcfe32e5842cedabc9c7eb8613/chrome/browser/resources/chromeos/chromevox/cvox2/background/editing_test.extjs [modify] https://crrev.com/bfb4db2020de72fcfe32e5842cedabc9c7eb8613/content/browser/accessibility/accessibility_action_browsertest.cc [modify] https://crrev.com/bfb4db2020de72fcfe32e5842cedabc9c7eb8613/third_party/blink/renderer/modules/accessibility/ax_object.cc [modify] https://crrev.com/bfb4db2020de72fcfe32e5842cedabc9c7eb8613/third_party/blink/web_tests/accessibility/press-works-on-text-fields.html |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krav...@chromium.org
, May 26 2016