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

Issue 768277 link

Starred by 1 user
Status: WontFix
Owner:
dbeam@chromium.org
Closed: Sep 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
dpa...@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Unnecessarily glimpse of Main menu side window is seen in chrome://history page .

Reported by rp...@etouch.net, Sep 25 2017 
Version: 63.0.3223.0 569732c0a96ec8d0c4c5df7f7012188696c7d37c-refs/heads/master@{#503964}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6)

What steps will reproduce the problem?
1. Launch chrome, navigate to Chrome://history and resize browser window such as Main Menu button appears.
2. Now click on Main menu button and then click on 'Clear browsing data' and 'Maximize' browser window
3. Now middle click on chrome://settings/clearBrowserData tab to close it and observe chrome://history page

Actual: Unnecessarily glimpse of Main menu side window is seen after closing chrome://settings/clearBrowserData tab
Expected: Unnecessarily glimpse of Main menu side window shouldn't be seen after closing chrome://settings/clearBrowserData tab

This is regression issue, broken in ‘M 58’ and will soon update other info :
Good build:58.0.3022.0
Bad build: 58.0.3023.0
Actual_video.mp4
543 KB View Download
Expected_video.mp4
877 KB View Download

Comment 1 by rp...@etouch.net, Sep 25 2017

Cc: dpa...@chromium.org
Labels: hasbisect-per-revision
Owner: dbeam@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 58.0.3022.0 (Revision: 452714).
Bad build: 58.0.3023.0 (Revision: 453044).

You are probably looking for a change made after 452726 (known good), but no lat
er than 452727 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/952fab9efa69cf3d0cc2a003762deec638199cdf..8c3875d433e85fc3868d5aa1f0350c0127175973

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

@dbeam- 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.

Suspect : https://chromium.googlesource.com/chromium/src/+/8c3875d433e85fc3868d5aa1f0350c0127175973

Thanks!

Comment 2 by dbeam@chromium.org, Sep 27 2017

Status: WontFix (was: Assigned)
this is likely because the new <paper-ripple> uses a CSS animation and is slowed down or cancelled more effectively, whereas the Polymer <paper-ripple> was using JS which is likely to need to keep running but at a slower rate (i.e. harder to suspend).

not anything we want/should do about this.  this saves power.
►

Sign in to add a comment