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

Issue 664904 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unwanted black line is seen in language selector dropdown of pinterest.com

Project Member Reported by sc00335...@techmahindra.com, Nov 14 2016

Issue description

Version: 56.0.2918.0 dev
OS: Ubuntu 14.04,Windows

What steps will reproduce the problem?
(1)Launch chrome and go to https://about.pinterest.com/en/browser-button-confirmation-page
(2)Scroll to bottom and select language selector dropdown >> Enter fullscreen and observe menu

Expected: No such black line should be seen near scrollbar.
Actual: Unwanted black line is seen beside scrollbar.

NOTE: By default black line is seen in windows.[No need to enter fullscreen]

This is a regression issue broken in M56. Will provide bisect info soon
 
Actual_black line.png
268 KB View Download
Expected_blackline.png
274 KB View Download

Comment 1 by ajha@chromium.org, Nov 14 2016

Labels: ReleaseBlock-Stable
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on the latest canary(56.0.2918.0) on Windows-10 but the same worked fine on Mac OS 10.11.6.
Manual Bisect Info:
====================
Good build:56.0.2915.0
Bad build:56.0.2916.0
Labels: -Needs-Bisect hasbisect-per-revision
Owner: qyears...@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,

Bisect Format:
---------------
You are probably looking for a change made after 431176 (known good), but no later than 431177 (first known bad).

CHANGELOG URL:
-----------------
https://chromium.googlesource.com/chromium/src/+log/3e072f5d6d65ae7d9ee65b5937775eb158871a61..a5d0b7d83a0ff8641db0c2269661721d494d6d77

From the CL above, assigning the issue to the concern owner 

@qyearsley- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Owner: schenney@chromium.org
That's definitely not the right change. I think it's me of flackr.

Reproduces on Win7, but not linux (which is odd, might be screen resolution or window size).

Comment 5 by ajha@chromium.org, Nov 18 2016

Cc: flackr@chromium.org
Rebisected this on Window-10 and below is the bisect result:
=============================================================

Last good build: 56.0.2891.7
First bad build: 56.0.2894.0(no intermediate builds in b/w)

Changelog:
==========
https://chromium.googlesource.com/chromium/src/+log/cc1a632036d1cdb215e9e55996006a904b1bf6eb..6c715c7a413e006594b26a2b59783d2d9d01f311

Indeed is related to schenney's change: https://codereview.chromium.org/2416453006

schenney@: Can we get an update on this issue.

Thank you!
Still able to reproduce the issue on win10 chrome version 57.0.2928.0

schenney@, Could you please take a look

Comment 7 by hdodda@chromium.org, Nov 30 2016

Cc: hdodda@chromium.org
Labels: Needs-Feedback
unabe to reproduce the issue on windows 10 using chrome M57 #57.0.2936.1 , No blackline is seen on the language dropdown. Seems the issue got fixed in latest canary.

Attached screenshot for reference.

@sc00335628-- Could you please re-check the issue on latest canary and update the thread.

Thanks!
664904.PNG
360 KB View Download
We tried reverting ~5 changes based on guessing but could not identify the fixing change. Am doing a git bisect on Win7 now.
Attempting to repro by syncing local build to commits as below distilled from above notes:

56.0.2894.0 = 13e8fdc9b6ad4c3eb78b2cd7f3e726a0cb3535b5
56.0.2918.0 = 55037222d2bbd10a352db5afc9371d164f573f3e
56.0.2916.0 = bc4708ac5f47e3a2bd7e581fe712a211b54384ba

All builds I've made locally so far do not show the issue. Perhaps there's a different third party dep on the release branch?

Will shift to trying bad versions noted in  http://crbug.com/663254 . We did see the issue on this same machine with I think official dev builds yesterday, and on auto-updating the dev build it went away.

It's possible I was inconsistent about passing '--enable-features=CompositeOpaqueScrollers', hmm.
Labels: -Needs-Feedback -ReleaseBlock-Stable
Status: WontFix (was: Assigned)
Still no sign of the bug on Win 10 Stable or Beta for several days. Closing since the stable version and future versions (tip of trunk) do not show the bug.

Sign in to add a comment