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

Issue 676428 link

Starred by 1 user
Status: Assigned
Owner:
dmazz...@chromium.org
Cc:
aleventhal@chromium.org
dmazz...@chromium.org
█ ggor...@vfogroup.com
█ jedwa...@vfogroup.com
Components:
EstimatedDays: ----
NextAction: 2016-12-21
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility

Blocked on:
issue 810762


Sign in to add a comment

IAccessibleText::scrollSubstringToPoint call in Chrome 50.0.2661.75 worked, but I am not seeing it fired in Chrome 51.0.2701.84.0 nor Chrome Canary

Project Member Reported by chaok@google.com, Dec 21 2016 
I am noticing another difference between Chrome 50.0.2661.75 and Chrome 51.0.2704.84.0 and Chrome Canary 57.0.2957.0  which is affecting the existing ZoomText Chrome interface code.
 
ZoomText depends on the IA2_EVENT_VISIBLE_DATA_CHANGED event to know when a page has changed or when a previously issued scroll command has completed.
 
This event is fired in response to a IAccessibleText::scrollSubstringToPoint call in Chrome 50.0.2661.75.  I am not seeing it fired in Chrome 51.0.2701.84.0 nor Chrome Canary 57.0.2957.0 .
 

Enviornnment Specs: 
Win10/64 and various versions of Chrome 32 bit edition.  The code that is dependent on this event in ZoomText has been in the field for many years now.

Comment 1 by chaok@google.com, Jan 9 2017

Cc: ggor...@vfogroup.com jedwa...@vfogroup.com
Labels: -Pri-2 Pri-1
Per Glen: "Any idea of when this issue will be addressed?
It represents a regression in ZoomText support of Chrome, so we’re eager for a resolution.
 
Thanks"

Comment 2 by dmazz...@chromium.org, Mar 27 2017

Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility

Comment 3 by dmazz...@chromium.org, Apr 21 2017

Components: UI>Accessibility>Compatibility

Comment 4 by dmazz...@chromium.org, Apr 21 2017

Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility

Comment 5 by lpalmaro@chromium.org, Aug 4 2017

Status: Available (was: Untriaged)

Comment 6 by dmazz...@chromium.org, Aug 4 2017

Labels: triage-lpalmaro

Comment 7 by nek...@chromium.org, Dec 13 2017

Cc: -nek...@chromium.org -lpalmaro@chromium.org aleventhal@chromium.org dmazz...@chromium.org
Labels: -triage-lpalmaro win-a11y
Owner: nek...@chromium.org

Comment 8 by dmazz...@chromium.org, Feb 16 2018

Owner: dmazz...@chromium.org

Comment 9 by dmazz...@chromium.org, Feb 16 2018

Labels: -Restrict-View-Google

Comment 10 by dmazz...@chromium.org, Feb 26 2018

Blockedon: 810762

Comment 11 by dmazz...@chromium.org, Feb 26 2018 

After some investigation it looks like JAWS is not calling scrollTo when it doesn't think a node is offscreen. That's because we're returning clipped bounds in accLocation (bug 810762).

I'm going to fix accLocation so that it returns the unclipped bounds of an object.

Comment 12 by benhenry@chromium.org, Aug 1

Status: Assigned (was: Available)
►

Sign in to add a comment