New issue
Advanced search Search tips

Issue 852206 link

Starred by 1 user
Status: Assigned
Owner:
yawano@chromium.org
Cc:
dtseng@chromium.org
osh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Task
Team-Accessibility



Sign in to add a comment

ArcA11y: use window coordinate instead of screen

Project Member Reported by yawano@chromium.org, Jun 13 2018 
Use window coordinate instead of screen coordinate for bounds of elements. For more background: https://crrev.com/c/1090598

Comment 1 by dtseng@chromium.org, Jun 15 2018 

Just as FYI, I tackled something similar in
https://chromium-review.googlesource.com/c/chromium/src/+/1083497

which fixed touch in Chrome OS accessibility when moving from a default landscape device to portrit. Incoming screen coordinate events were converted to local window coordinates for the purposes of interpreting gestures and other state reasoning. So, I agree with the title of this bug.

Comment 2 by dtseng@chromium.org, Jun 15 2018 

Also, I think the more correct statement should be:
use the root window bounds for elements, but set the AXRelativeBounds with the offset container correctly.

In the case of this root window, it should have been offset by a containing window that knows about the ChromeVox Panel.
►

Sign in to add a comment