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

Issue 735865 link

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



Sign in to add a comment

Regression : While autoscroll, mouse cursor does not change according to the scolling direction.

Reported by avsha...@etouch.net, Jun 22 2017 
Chrome version : 61.0.3138.0 (Official Build) d2d3a3975e9c7f3c5c62ef0ecad2683332894600-refs/heads/master@{#481386} 32/64 bit
OS : Windows(7,8,10)

Test URL : http://ncu.rcnpv.com.tw/Uploads/20131231103232738561744.pdf

What steps will reproduce the problem?
1. Launch chrome and navigate to above test URL.
2. Try to autoscroll the pdf file through middle click and observe the mouse cursor while autoscrolling.

Actual Result : Mouse pointer does not change according to the scolling direction.

Expected Result : Instead, mouse cursor should change into 'Up/Down' or 'Left/Right Arrow' pointer, depending on the direction in which pdf is being auto-scrolled.

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 : Issue is not reproducible in Mac(10.11.6, 10.12.3) and Linux(14.04 LTS) OS.
Actual_Autoscrolling.mp4
2.6 MB View Download
Expected_Autoscrolling.mp4
1.6 MB View Download

Comment 1 by jmukthavaram@chromium.org, Jun 22 2017

Cc: jmukthavaram@chromium.org
Labels: hasbisect-per-revision
Owner: aelias@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 7 using chrome latest Canary-61.0.3138.0.
Manual Bisect:
--------------
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 & reassign to the right owner if it is not related to your change.

Thank you..!!

Comment 2 by aelias@chromium.org, Jun 28 2017 

I have a fix up at https://codereview.chromium.org/2961003002
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 29 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/be5aadf1dfe860773906916f583270793e45db3d

commit be5aadf1dfe860773906916f583270793e45db3d
Author: aelias <aelias@chromium.org>
Date: Thu Jun 29 02:09:08 2017

Prevent plugins from changing mouse cursor during middle-click autoscroll.

Cursor updates were suppressed in EventHandler, but this doesn't
work for plugins which call SetCursorForPlugin directly on ChromeClient.
This was a preexisting bug, but it got worse with the recent rewrite
because the bug used to be mostly covered up by the old implementation
pushing cursor updates at 60fps.

BUG= 735865 

Review-Url: https://codereview.chromium.org/2961003002
Cr-Commit-Position: refs/heads/master@{#483259}

[modify] https://crrev.com/be5aadf1dfe860773906916f583270793e45db3d/third_party/WebKit/Source/core/exported/WebViewTest.cpp
[modify] https://crrev.com/be5aadf1dfe860773906916f583270793e45db3d/third_party/WebKit/Source/core/page/AutoscrollController.cpp

Comment 4 by aelias@chromium.org, Jun 29 2017

Status: Fixed (was: Assigned)

Comment 5 by avsha...@etouch.net, Jul 11 2017

Labels: TE-Verified-61.0.3153.0 TE-Verified-M61
Update :
Retested above issue in Windows(7,8,10) OS with latest Dev# 61.0.3153.0 build and issue is not reproducible. It is fixed and working a intended.

Thank you..
►

Sign in to add a comment