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

Issue 748383 link

Starred by 1 user
Status: WontFix
Owner:
█ aelias@chromium.org
inactive
Closed: Jul 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
jmukthavaram@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression : Unwanted movement is seen in chrome://downloads, when moving mouse horizontally across the page.

Reported by avsha...@etouch.net, Jul 25 2017 
Chrome version : 62.0.3166.0 (Official Build) dd5214f6efc02a459d85f09cb9d09383083ea27d-refs/heads/master@{#489161} 64 bit
OS : Windows (7,8,10)

What steps will reproduce the problem?
1. Launch chrome, navigate to chrome://downloads and generate 4 - 5 download records such that vertical scroll bar appears on the page.
2. Now middle click on the page and move mouse from left to right and vice versa.
3. Observe download records.

Actual Result : Unwanted movement of download records is seen when mouse is moved horizontally across the page.

Expected Result : Download records should not move when mouse is being moved from left to right and vice versa.

This is a regression issue broken in ‘M-61’, below is the Manual Regression range and will soon update other info.
Good build : 61.0.3132.0
Bad build : 61.0.3133.0

Note :  Above issue is not reproducible in Mac(10.11.6, 10.12.3) and Linux(14.04 LTS) OS.
Actual_Downloads.mp4
977 KB View Download
Expected_Downloads.mp4
764 KB View Download

Comment 1 by jmukthavaram@chromium.org, Jul 25 2017

Cc: jmukthavaram@chromium.org
Labels: hasbisect-per-revision ReleaseBlock-Stable
Owner: aelias@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 7 using chrome latest Canary-62.0.3166.0 .
Manual bisect info:
-------------------
Good build : 61.0.3132.0-Revision-479900
Bad build : 61.0.3133.0-Revision-480259

Per revision bisect info:
-------------------------
You are probably looking for a change made after 479930 (known good), but no later than 479931 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspectas some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/9ede2cde5727eecdb377b57b32c5226d1d41c8ce..5971e47dc08dbb773f58fd6fb13b1df7917fd295

Possible suspect:
----------------
https://chromium.googlesource.com/chromium/src/+/5971e47dc08dbb773f58fd6fb13b1df7917fd295

aelias@Could you please take a look and reassign to the right owner if it is not related to your change.

since it is regressed recently,marking it as Release block stable label.Please remove if it is not required.
Thank you..!!

Comment 2 by aelias@chromium.org, Jul 25 2017

Labels: -Pri-1 Pri-3
Status: WontFix (was: Assigned)
> since it is regressed recently,marking it as Release block stable label.

That doesn't fit the new policy: https://chromium.googlesource.com/chromium/src.git/+/master/docs/process/release_blockers.md#Regressions says "Regressions should follow the same guidelines as listed above; an issue should not be tagged as a release blocker simply because it is a regression."

The severity of this isn't high enough and it's probably page-specific, so I'm not planning to fix this.
►

Sign in to add a comment