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

Issue 652588 link

Starred by 2 users
Status: WontFix
Owner:
alemate@chromium.org
Closed: Nov 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : 'Accessibility' Link is not fully seen after navigating from EULA screen

Project Member Reported by mmanchala@chromium.org, Oct 4 2016 
Version: 55.0.2878.0/8860.0.0 dev channel Daisy,Peppy,Blaze
OS: Chrome OS

What steps will reproduce the problem?
(1)Recover build ->IN EULA Screen  Click 'ACCEPT AND CONTINUE' Button
(2)Now on "Chrome Updates automatically to freshest version" screen observe 'Accessibility' Link at left bottom  (Please refer screenshot)

Expected: 'Accessibility' Link  in "Chrome Updates automatically to freshest version" screen should be seen clearly
Actual: Instead 'Accessibility' Link is seen misplaced i.e. not fully seen

This is a Regression issue as same is working fine in 53.0.2785.100/8530.80.0 peppy.

Issue is seen with New material design OOBE. Hence assigning to @alemate.

@alemate: Please confirm the behavior.
Actual_Accessibility.jpg
110 KB View Download
Expected_Link.jpg
168 KB View Download

Comment 1 by mmanchala@chromium.org, Oct 4 2016

Labels: ReleaseBlock-Stable
Adding Stable Blocker as this is a recent Regression.Please remove if not required.

Comment 2 by bhthompson@google.com, Nov 15 2016 

Any update on this? This is marked as a stable blocker and we are nearing R55 stable, however there has been no update for a month.

Comment 3 by zalcorn@chromium.org, Nov 15 2016

Labels: -M-55 M-56
New Material Design OOBE is not launching until 56, so this should not be a blocker for 55. I'll update the label.

Comment 4 by alemate@chromium.org, Nov 18 2016

Labels: -M-56 M-55
This is not in material design.
Setting back to 55.

Comment 5 by alemate@chromium.org, Nov 19 2016

Status: WontFix (was: Assigned)
I cannot reproduce it neither in 56 no in 55. 

55.0.2883.57 doesn't have this problem on Peppy.
►

Sign in to add a comment