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

Issue 656964 link

Starred by 1 user
Status: WontFix
Owner:
dbeam@chromium.org
Closed: Oct 2016
Cc:
█ hdodda@chromium.org
nyerramilli@chromium.org
█ brajkumar@chromium.org
█ tkonch...@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: Unnecessary movement is observed on 'Reset' overlay in device mode after clicking on it.

Reported by rk...@etouch.net, Oct 18 2016 
Chrome Version: 55.0.2883.19 (Official Build) 2dbf3618e498fe353db70354fd79181dd8286aa1-refs/branch-heads/2883@{#167}(32/64 Bit)
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.10.5, 10.11.4)

What steps will reproduce the problem?
(1) Launch chrome, navigate to chrome://md-settings/resetProfileSettings?origin=userclick 
(2) Open dev tools window on it, then click on 'Toggle device mode' icon
(3) Now click on reset overlay and observe.

Actual: Unnecessary movement is observed on reset overlay after clicking on it.

Expected: No such movement should observed on reset overlay after clicking on it.

This is a regression issue broken in M-55, will soon update the other info.

Manual Regression Range:
Good Build: 55.0.2880.0 
Bad Build: 55.0.2881.0
Reset_Actual.mp4
591 KB View Download
Reset_Expected.mp4
347 KB View Download

Comment 1 by hdodda@chromium.org, Oct 18 2016

Cc: hdodda@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:55.0.2880.0(Revision: 422654).
Bad build: 55.0.2881.0 (Revision:423030).

You are probably looking for a change made after 422895 (known good), but no later than 422896 (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/c537c6daa5b25f823e34e0359e15e0ccce019e7f..c59443f0412c8dd63a59f0e2ce556bfd7151e1d0


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.

Review-Url: https://codereview.chromium.org/2382243003

Note : Issue is seen in latest chrome canary M56 # 56.0.2894.0 .

Thanks!

Comment 2 by brajkumar@chromium.org, Oct 27 2016

Cc: brajkumar@chromium.org
Just to update, issue is observed on Ubuntu 14.04 for chrome version 56.0.2902.0. 

@dbeam: Gentle ping, This issue is marked as P1 for M55 milestone, can we get any update on this bug?

Issue is broken in M55 and it's already in Beta and will be pushed to stable soon.

Thanks.!

Comment 3 by dbeam@chromium.org, Oct 27 2016

Labels: -Pri-1 -M-55 Pri-2
Status: WontFix (was: Assigned)
ok, so a few things:

1) this code doesn't run on mobile and dev tools changing to simulate mobile (while the page is running) is not helpful.  stop testing this

2) any type of flicker like this that's recoverable will never be P1

3) md-settings is locked to canary channel and wont be shipping in M55, so it's not helpful to make noise about this
►

Sign in to add a comment