New issue
Advanced search Search tips

Issue 856506 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 11
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:Unwanted shadow stays on tab after closing context menu.

Reported by vku...@etouch.net, Jun 26 2018

Issue description

Chrome Version: 69.0.3473.0 (Official Build)Revision cd23eb9e98a965ea157e23052bb62553e5d520d5-refs/branch-heads/3473@{#1} (32/64-bit)
OS: Windows 7

What steps will reproduce the problem?
(1)Launch chrome and open 2 NTP
(2)Right click on tab of other ntp such that context menu appears.
(3)Now click on 2nd ntp tab to close context menu and observe the previous tab.


Actual: Unwanted shadow stays on tab after closing context menu.

Expected: No such shadow should be seen on tab after closing context menu.

This is a regression issue broken in 'M69' and below is the manual regression range
Good Build: 69.0.3472.3(Revision:569949)
Bad Build:  69.0.3473.0(Revision:570288)
 
Actual_Tab.png
112 KB View Download
Actual_Tabstrip.mp4
297 KB View Download

Comment 1 by vku...@etouch.net, Jun 26 2018

Cc: pbomm...@chromium.org
Labels: RegressedIn-69 FoundIn-69 Target-69 hasbisect
Owner: kylixrd@chromium.org
Status: Assigned (was: Unconfirmed)
(Unable to narrow down the range using per-revision bisect,hence providing bisect using old script)
Narrow bisect URL:
You are probably looking for a change made after 570216 (known good), but no later than 570235 (first known bad).
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/3c16d9d466102e0839cad4e70cea850107143ca4..64c540a750df6adb453c0f8e6e63800d8948d04c

Suspecting: r570226 ?

@kylixrd: 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.

Note: This is Win 7 specific issue and not seen on Windows(8,8.1,10), Mac OS(Mac (10.12.6, 10.13.1, 10.13.5, 10.13.6) & Linux(14.04 LTS).
Cc: kylixrd@chromium.org
Labels: -Pri-1 Proj-MdRefresh Pri-2
Owner: bsep@chromium.org
Status: WontFix (was: Assigned)
I just checked this and it doesn't seem to reproduce? It may have been accidentally fixed by something else. Closing.

Sign in to add a comment