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

Issue 812999 link

Starred by 1 user
Status: Assigned
Owner:
zork@chromium.org
Cc:
ajha@chromium.org
dmazz...@chromium.org
█ brajkumar@chromium.org
tbuck...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Non-Regression:Border Traces of ubertray are seen even after closing in Cyan device

Project Member Reported by rkalavakuntla@chromium.org, Feb 16 2018 
Chrome Version: 66.0.3344.0/10408.0.0 dev channel Cyan
OS: Chrome OS

What steps will reproduce the problem?
(1)Recover Build >> In OOBE screen,go to Ubertray/Accessibility 
(2)Enable 'High contrast mode' and 'Screen magnifier'
(3)Now close the  ubertray and observe traces of ubertray borders(Kindly refer video)

Actual:Border Traces of ubertray are leftover even after closing it
Expected:No such traces should be seen

This is a Non-Regression issue seen from M-62

Note:
1.Issue is not seen in Linux,Windows and other chrome OS like Glimmer,Celes..
2.Issue is Cyan specific
Border traces.jpg
2.9 MB View Download
Actual.mp4
9.4 MB View Download

Comment 1 by tbuck...@chromium.org, Feb 16 2018

Owner: zork@chromium.org
Status: Assigned (was: Untriaged)
@zork, any idea where to start on this one? Seems like it might be tied to the a11y features rather or graphics rather than system menu.

Comment 2 by zork@chromium.org, Feb 16 2018 

My guess would be that there's a border that doesn't invalidate the pixels behind it in the compositor.  This could be caused by an off by one error or rounding when changing the the effective pixel scale with the magnifier.

Comment 3 by leberly@chromium.org, Jul 18

Labels: MagnifierCrOS
►

Sign in to add a comment