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

Issue 795985 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Blink does not set correct anchor and focus objects for mouse triggered selections

Project Member Reported by katie@chromium.org, Dec 19 2017

Issue description

For example, highlight chrome://settings/manageAccessibility from "Enable Chromevox..." through "select content to be read aloud" (see screenshot).

The focused node anchor and focus object are the same! The focusObject should be a different line of text.

focusedNode acquired from chrome.automation.getFocus:

focusedNode.root.anchorObject.name
"Enable ChromeVox (spoken feedback)"

focusedNode.root.focusObject.name
"Enable ChromeVox (spoken feedback)"

More info:
focusedNode.anchorOffset
0

focusedNode.anchorAffinity
"downstream"

focusedNode.focusOffset
34

focusedNode.focusAffinity
"downstream"
 
Screenshot from 2017-12-18 17:29:27.png
46.3 KB View Download

Comment 1 by dtseng@chromium.org, Dec 19 2017

How are you setting selection? The anchor and focus objects come as a result of DOM selection. In chrome.automation, there are two ways to trigger a selection action:
- chrome.automation.setDocumentSelection
- on an AutomationNode, call setSelection

Comment 2 by katie@chromium.org, Dec 19 2017

Labels: OS-Chrome
I'm clicking and dragging with the mouse. More nodes are highlighted visually when I click and drag than are coming through on the automation tree, on this page in particular.

Comment 3 by dtseng@chromium.org, Dec 19 2017

Summary: Blink does not set correct anchor and focus objects for mouse triggered selections (was: chrome.automation doesn't always get selection correct)
Clarifying title. This is information we get from Blink, so the bug is almost certainly there.

Comment 4 by dtseng@chromium.org, Dec 19 2017

Cc: nek...@chromium.org
+ nektar, who was the last one who was looking at Blink selections in detail.

Comment 5 by katie@chromium.org, Jan 16 2018

Cc: lpalmaro@chromium.org
I've got another two example of the same type of bug:

-------------------------Second example------------------------------

Click and drag with the mouse to select everything on the chrome://settings page, starting at the Network header. Only the Network header node appears to be selected in the Automation tree.

focusedNode acquired from chrome.automation.getFocus:

focusedNode.root.anchorObject.name
"Network"

focusedNode.root.focusObject.name
"Network"

focusedNode.root.anchorOffset
0

focusedNode.root.focusOffset
7

Expected result: the focusedNode is different from the anchorNode, and is "Open a specific page or set of pages" or something further down the page where highlighting stopped.


-------------------------Third example------------------------------
Click and drag to select text in chrome://settings, starting at "Ethernet", through "Add connection".

focusedNode acquired from chrome.automation.getFocus:

focusedNode.root.anchorObject === focusedNode.root.focusObject
focusedNode.root.anchorOffset === focusedNode.root.focusOffset

Expected:
The offsets and focus/anchor objects are not exactly the same, since a portion of the page is selected.

Labels: a11y-Settings
Status: Available (was: Untriaged)

Sign in to add a comment