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

Issue 794895 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Unable to drag text links to 'Search History' search box in chrome://history/ page.

Reported by rp...@etouch.net, Dec 14 2017

Issue description

Version: 63.0.3239.108 d2626860fae283daee484943e6820af18fc73fd9-refs/branch-heads/3239@{#676}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.1)

What steps will reproduce the problem?
1. Launch chrome, navigate to chrome://history/ and drag all text links on LHS to 'Search History' search box,observe
 
Actual: Unable to drag all text links(Chrome History,Tabs from other devices,Clear Browsing Data) to 'Search History' search box
Expected: Should be able to drag all links(Chrome History,Tabs from other devices,Clear Browsing Data) to 'Search History' search box

This is regression issue, broken in ‘M 60’ and below is the bisect info :
Good build: 59.0.3071.0  (Revision: 464642).
Bad build: 60.0.3072.0 (Revision: 464836).

You are probably looking for a change made after 464697 (known good), but no later than 464698 (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/188c1056bbfb9c98eca691c12f5641d4204f6066..0f65d25a4097959d977dbb1077717323438240a6

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

@hugoh- 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/+/0f65d25a4097959d977dbb1077717323438240a6

Thanks!
 
Actual_video.mov
1.4 MB Download
Expected_video.mov
1.1 MB Download

Comment 1 by hu...@vewd.com, Dec 14 2017

Owner: dbeam@chromium.org
dbeam@, could you take this bug? I guess it can be closed as a WontFix.

Comment 2 by hu...@vewd.com, Dec 14 2017

Owner: dpa...@chromium.org
Assigning over to dpapad@ because I see that dbeam@ is no longer working on Chrome.

Sign in to add a comment