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

Issue 802763 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
STS
Team-Accessibility



Sign in to add a comment

Getting selection in docs results in rootWebArea with no children.

Project Member Reported by katie@chromium.org, Jan 16 2018

Issue description

Selection in docs seems odd -- select text in the body of the document, and the focused object is a rootWebArea with no children.

Doc example: https://docs.google.com/document/d/1Cw2jOf0Tcnq1zWOV93XYIF6u2UTS37kBJJS-hTsTllI/edit


> var focused;
undefined
> chrome.automation.getFocus(function(f) {focused = f;})
undefined
> focused.root.focusObject.role
"rootWebArea"
> focused.root.focusObject.children
[]
 

Comment 1 by katie@chromium.org, Feb 1 2018

Blocking: 801410

Comment 2 by katie@chromium.org, Feb 15 2018

Blocking: -801410
This is no longer blocking. We will use the clipboard as a work-around.

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

Labels: OS-Chrome
Status: Available (was: Untriaged)

Comment 4 by katie@chromium.org, Mar 19 2018

Components: UI>Accessibility>SelectToSpeak
Good vibes
Labels: STS_selection
This bug requires improvements to selection and may automatically be fixed when relevant selection fixes are available through the automation API.

Sign in to add a comment