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

Issue 787785 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : 'Accessibility' header section moves down on selecting 'Accessibility' option in Uber Tray Panther Device

Project Member Reported by mmanchala@chromium.org, Nov 22 2017

Issue description

Chrome Version: 64.0.3274.0/10151.0.0 dev channel Panther
OS: Chrome

What steps will reproduce the problem?
(1)Sign into User -> Click on Uber Tray
(2)Now click on 'Accessibility' option -> observe  'Accessibility' header section moves down so that unable to view options in  'Accessibility' (Please refer video and Screenshot)

Expected: On clicking 'Accessibility' should be able to view options in  'Accessibility' section
Actual: Instead unnecessarily 'Accessibility' header section moves down so that unable to view options in 'Accessibility'

This is Regression Issue as same is working fine in 63.03239.50/10032.39.0 Beta-channel Panther

@tbuckley : Please confirm the Issue

Note: 
1.Issue is also seen on 64.0.3270.0/10134.0.0 dev-channel Panther
2.Issue is working fine in Minnie and Swanky
3.Issue is seen for 'Keyboard' options, 'Network' options and 'Bluetooth'
 
Actual_NoOptions.webm
5.4 MB View Download
Actual_NoOptions.jpg
363 KB View Download
Expected_Options.webm
5.0 MB View Download
Expected_Options.png
4.9 MB View Download
Issue is also seen on 64.0.3274.0/10154.0.0 dev-channel Zako 
Hi, this is tagged as a beta blocker for M64.  We're not that far out and this bug hasn't been updated in a while.  Ping?  Thanks...

M64 beta is targeted for next Tuesday (12-Dec); anything we can do to close this out and/or retag as stable block is appreciated.   I'll ping the owner as well.  Thanks!

Status: WontFix (was: Assigned)
I'm unable to repro on 65.0.3286.0 canary Eve or 64.0.3282.11 dev Caroline, so closing as WontFix.
Status: Assigned (was: WontFix)
C#4>
Able to reproduce the issue on 64.0.3282.14/10176.8.0 and on 65.0.3287.0/10196.0.0 dev-channel Zako.


Can we look back into this?  The M65 revs are fairly recent so should be reconfirmed.  
Please re-evaluate today (Monday, 11-Dec) re: Beta Blocker Status.  We're targeting Beta for tomorrow, so please update if a) this isn't blocking, b) the impacted boards can be identified, c) this is resolved / not reproducible, d) a merge / fix can be submitted today.  Thanks!

Comment 8 by gkihumba@google.com, Dec 12 2017

Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
Marking this as RBS as it should not gate beta.
Cc: tbuck...@chromium.org
Owner: zork@chromium.org
@zork, is there someone on your team who can look at this since it is Release-Block-Stable? It seems to only repro on certain devices (eg. Zako but not Eve).
Cc: kbleicher@chromium.org pucchakayala@chromium.org dhadd...@chromium.org
 Issue 798903  has been merged into this issue.

Comment 11 by josa...@google.com, Jan 20 2018

Cc: warx@chromium.org
Any update on this case? 

btw. I can't repro on Coral device (perhaps external display only)

Comment 12 by warx@chromium.org, Jan 20 2018

Cc: osh...@chromium.org afakhry@chromium.org

Comment 13 by zork@chromium.org, Jan 22 2018

Cc: zork@chromium.org
Owner: x...@chromium.org
Daisy, could you have someone look into this?

Comment 14 by x...@chromium.org, Jan 22 2018

Cc: x...@chromium.org
Owner: minch@chromium.org
minch@, I think you looked into similar issues before. Could you take a look?

Comment 15 by minch@chromium.org, Jan 24 2018

I can repro this on Zako. Will do the bisecting first.

Comment 16 by minch@chromium.org, Jan 25 2018

Cc: minch@chromium.org
Owner: yoshiki@chromium.org
Through bisecting, the issue was caused by
https://chromium-review.googlesource.com/c/chromium/src/+/727379

Guess the same reason as  issue 779992 

yoshiki@, please help take a look. Thanks.
Ping as RBS for M64.  Progress?
Status: Started (was: Assigned)
I confirmed the issue:

The commit 3ae2446be3d11e6393c0bc8567f953212babc63c solves the issue. Let me merge this to M64.
Merged: https://chromium.googlesource.com/chromium/src.git/+/04c03c427c9ab5ccb28e01969b2cf5a1cfb9752d

Could you check the fix after the next version is released?
Merge requests should be made with the appropriate labels for TPM review.  They're not automatically approved after branch.  Was this CL submitted for review and approved via a different bug, etc.?  

This appears to be a fairly big change. Is the scope limited to a specific board or more generalized?  We may need to revert if this updated isn't critical for M64 stable.
The merge was originally requested and approved in the separated issue in  crbug.com/789833 .
Please verify in the latest beta.  Thx
As I tested on 64.0.3282.114 (Chrome OS 10176.68.0 on samus), it's fixed.
Labels: -ReleaseBlock-Stable
Removing stable blocker since confirmed fixed.
Status: Fixed (was: Started)

Sign in to add a comment