Issue metadata
Sign in to add a comment
|
Blink does not set correct anchor and focus objects for mouse triggered selections |
||||||||||||||||||||||
Issue descriptionFor 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"
,
Dec 19 2017
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.
,
Dec 19 2017
Clarifying title. This is information we get from Blink, so the bug is almost certainly there.
,
Dec 19 2017
+ nektar, who was the last one who was looking at Blink selections in detail.
,
Jan 16 2018
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.
,
Sep 7
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Dec 19 2017