New issue
Advanced search Search tips

Issue 835251 link

Starred by 3 users
Status: Assigned
Owner:
bsep@chromium.org
Cc:
pbos@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
pkasting@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression : Unwanted patch is seen in tab strip after maximizing and restoring down browser window.

Reported by avsha...@etouch.net, Apr 20 2018 
Chrome Version : 67.0.3396.13 (Official Build) b3152cbcc026b1404e0a4bcd161244bcf009650b-refs/branch-heads/3396@{#152} 32/64-bit
OS : Windows 10

What steps will reproduce the problem?
1. Freshly install chrome, launch it and maximize the browser window.
2. Open NTP, hit F11 (to go into fullscreen mode), press 'Ctrl + Shift + M' and click on 'Manage people'.
3. Select and remove the current person.
4. Click on browser's maximize button and then click on resotore down button.
5. Repeat step 4 one more time and observe. (Kindly review attached screencast for reference)

Actual Result : Unwanted patch is seen in tab-strip after maximizing and restoring down.

Expected Result : Patch should not appear in tab-strip after maximizing and restoring down.

This is a regression issue, broken in M-67 and providing the bisect using per-revision script:
Good Build : 67.0.3377.0 (Revision : 544611)
Bad Build : 67.0.3378.0 (Revision : 544931)

You are probably looking for a change made after 544787 (known good), but no later than 544788 (first known bad).

CHANGE-LOG URL:
https://chromium.googlesource.com/chromium/src/+log/cd54fed5e109370d5dd84d59e01819c1b786aefd..979c3c4d8355e456339c648db65c8201991b43af

Suspect : https://chromium.googlesource.com/chromium/src/+/979c3c4d8355e456339c648db65c8201991b43af

@Bret : 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 : 
1. This is Win-10 specific issue and it can not be reproduced on Win(7,8,8.1), Linux(14.04 LTS) and Mac(10.12.6, 10.13.1, 10.13.5) OS.
2. Issue is also observed in Canary build #68.0.3401.0
Actual_Result.mp4
625 KB View Download
Expected_Result.mp4
525 KB View Download

Comment 1 by pbos@chromium.org, Apr 20 2018

Cc: pbos@chromium.org
Labels: Needs-Feedback
I tried reproducing this on Windows 10 on a SurfaceBook and my desktop machine without any luck.

* Do you reproduce this all the time?
* Are all steps required here (freshly installed doesn't sound relevant)?
* Do you have another Windows 10 machine to test on? If so, does it reproduce there too?

I see blue borders flash by but the window eventually ends up repainting itself, so the blue border is temporary for me (and covers the whole top part of the window).

Comment 2 by avsha...@etouch.net, Apr 23 2018

Labels: -Needs-Feedback
Hi @pbos

Tried to reproduce issue with canary build #68.0.3403.0 on other win-10 machines and got following results:
1. Frequency of occurrence of this  issue 4  out of 5.
2. Yes, at our end fresh installation is required to reproduce the issue.
3. Tried on other three Win-10 machines including touch device and issue is observed on all three machines.

Note : 
a. After step 4, drag browser window slightly down and then carry on with step 5 and see if it helps to repro the original issue.
b. In rest of the win-10 machines, yellow patch is observed instead of blue.
Win-10_Title_bar.mp4
853 KB View Download

Comment 3 by vineetha...@etouch.net, Nov 14

Labels: Hotlist-DesktopUIChecked Hotlist-DesktopUIValid
Mass UI Triage Update:

Still able to reproduce the above issue on Win 10 OS using latest canary #72.0.3610.0. Please find the screen shot for reference.

@bsep: Could you please take a look into this issue.

Thank you
Canary_Behaviour.mp4
677 KB View Download

Comment 4 by bsep@chromium.org, Nov 14

Labels: -Pri-1 Pri-3
It's only on a fresh install, so I'm not too concerned with tracking this down right now.
►

Sign in to add a comment