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

Issue 727665 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:Emulated history content is not draggable

Project Member Reported by keerthan...@techmahindra.com, May 30 2017

Issue description

Chrome Version:60.0.3112.7 dev
OS:Ubuntu 14.04, Windows

Pre-condition: Make sure you have some history.

What steps will reproduce the problem?
(1)Launch chrome and open devtools in chrome://history
(2)Click on toggle device toolbar and drag the emulated window to the extreme left
(3)Now try dragging emulated view using mouse(Kindly refer the video)

Expected:Emulated history content should be draggable
Actual:Emulated history content is not  draggable

This is a Regression issue seen from M-59

Manual Bisect Info:
==================
Good Build:59.0.3041.0 dev
Bad Build: 59.0.3042.0 dev

NOTE: Issue is also seen for chrome://md-settings page.
 
historyActual.ogv
1.8 MB View Download
historyExpected.ogv
2.3 MB View Download

Comment 1 by ajha@chromium.org, May 30 2017

Labels: -M-60 M-59 OS-Mac
Status: Untriaged (was: Unconfirmed)
Issue is reproducible on the latest canary version: 61.0.3114.0 as well.
Labels: -Needs-Bisect hasbisect-per-revision
Owner: dpa...@chromium.org
Status: Assigned (was: Untriaged)
Using the per-revision bisect providing the bisect results,

Good Build: 59.0.3041.0 (Revision: 456562).
Bad Build: 59.0.3042.0  (Revision: 456934).

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

CHANGELOG URL:

https://chromium.googlesource.com/chromium/src/+log/83e2a57d77aff467d03f212ae3076400b172f2ea..88db8a1e6b522e67bfe49c1789dcde1f9d32ac22

From the CL's above, suspecting the below change and assigning the issue to the concern owner 

Suspect : https://codereview.chromium.org/2747783003

@dpapad- 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/2856223005


Thanks!

Comment 3 by dpa...@chromium.org, May 30 2017

Cc: dbeam@chromium.org
Labels: -Pri-1 Pri-2
Status: WontFix (was: Assigned)
Device mode is not important for chrome://history, AFAIK. I don't see any action item coming out of this issue, since it works as expected on Desktop.

Sign in to add a comment