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

Issue 608667 link

Starred by 1 user
Status: WontFix
Owner:
█ robhogan@chromium.org
Use other robhogan account instead.
Closed: May 2016
Cc:
nyerramilli@chromium.org
█ ashej...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unnecessary scrollbar appears in the drop down menu.

Reported by jshan...@etouch.net, May 3 2016 
Chrome Version: 52.0.2723.0 (Official Build) 5e216d9b62275101c30f4a5cb2174bb68970ef3c-refs/heads/master@{#391139} (64-bit)
OS: Windows (7,8,8.1,10), Mac OS X 10.11.14, Linux (14.04 LTS)
Test URL: gmail.com

Steps:
1. Launch chrome and navigate to the above URL and go to settings and set the display density to "Compact".
2. Click the dropdown icon next to Inbox label and observe the dropdown.

Actual result:   Unnecessary scrollbar appears in the dropdown menu.
Expected result: Unnecessary scrollbar shouldn't appear in the dropdown menu.

This is a regression issue broken in 'M50'

Manual Regression range:
Good Build: 50.0.2657.0
Bad Build:  50.0.2658.0

Narrow Bisect:
https://chromium.googlesource.com/chromium/src/+log/23d6a478c76d5e31c8bb47fa31bd53f619b536bd..4d23825e7f84e0057442cd94f4870547da64c483?pretty=fuller&n=100

Suspecting: 376962?
Actual_Dropdown.png
90.3 KB View Download
Expected_Dropdown.png
91.3 KB View Download

Comment 1 by robho...@gmail.com, May 4 2016

Labels: -OS-Linux
I can't reproduce this on:

Chromium	52.0.2719.0 (Developer Build) (64-bit)
Revision	66bea1de4dbc4a18684655979360031c14ad97a9-refs/heads/master@{#390175}
OS	Linux 
Blink	537.36 (@66bea1de4dbc4a18684655979360031c14ad97a9)

Comment 2 by robho...@gmail.com, May 4 2016

Labels: OS-Linux
Oh right, you have to mouse-over the final item. I can reproduce it now.

Comment 3 by robhogan@chromium.org, May 9 2016

Status: WontFix (was: Assigned)
Our rendering matches FF and Presto. Haven't tried Edge. I think our behaviour is correct here - the page was depending on broken behaviour.
►

Sign in to add a comment