I have used Logitech mouse.

Could this be related to https://bugs.chromium.org/p/chromium/issues/detail?id=597081 ?

This is working fine on stable build 7834.66.0/49.0.2623.111, Beta Build 7978.36.0, 50.0.2661.57

This issue may be related to  issue 597081 , but i filed a new one as i am unable to scroll through the PDF using an external mouse at all.

Using the mouse pad seems to be working, but there is a lag while scrolling through the PDF and i do not see any janky thing as described in  issue 597081 

Is this still being seen on the latest R51 builds?  Issue 587081  has been fixed. 

Unable to reproduce this issue on Latest M51 branched Build - 51.0.2704.15 [Paine & Peppy] using the externally connected mouse wheel.

Lag is observed while scrolling using the track pad of the device is still observed on Peppy device  - 51.0.2704.15

+oshima

Is there anything left regarding lag while scrolling on the touch pad, or are we back to normal here?

If this is what we expect I am tempted to call this fixed (or dupe of 597081).

It's unclear to me what was the original issue. "very head" is ambiguous. Best way is to upload the video.

If this happens only with external mouse, 597081 is unrelated, but it's hard to tell from the description in #1.

It sounds like we have achieved the main goal here, moving this up to stable so we can review later if needed, but I think we can probably just close this.

Is this still valid?

Unable to repro and no new feedback. Please feel free to reopen if you see this issue again.

Reopening the issue as this is seen on M52 build - 8350.2.0, 52.0.2743.0 [Candy Device]

http://www.theicn.org/documentlibraryfiles/PDF/20100210093138.pdf

Unable to scroll at all using the externally connected Logitech mouse.

Reproduce the issue on 8350.3.0, 52.0.2743.0 - Parrot.  Unable to scroll PDF files by Logitech mouse.

If this happens on Parrot, then it should be unrelated to my dsf work.

to adlr@ for mouse related issue.

+thestig@ in case he knows an issue with mouse wheel scrolling in pdf.


Here is the environment I tested, on which I could not reproduce this.

Google Chrome	52.0.2727.0 (Official Build) dev (64-bit)
Revision	99526c41079e7de62a26a9c2cb9619a78f4df60a-refs/heads/master@{#392210}
Platform	8302.0.0 (Official Build) dev-channel stumpy

Mouse: DELL mouse, Samsung mouse.

Given this is releaseblock-stable this should probably be Pri-1, if this is really Pri-2 we should punt this to 52. 

Andrew, is there anything else we should be doing on this one at this point?

We have a stable RC build on Wednesday, so if this is really a blocker we need to get this fixed and merged in the next 24 hours. 

If this does not repro reliably perhaps this should be punted to R52 or a second stable if we can get a fix?

I havent't gotten to look into this, but I also wonder if this is happening b/c PDFs don't scroll until the new content to be shown is fully rendered. If the PDF is complex, scrolling may seem to not work well.

Can I see this failing in person? I could help triage.

Has anyone been able to reproduce this lately?

This is still seen on 8350.14.0 / 52.0.2743.19 - Paine 

I tried this out on an 8172.45 Chell, using an extremely generic old HP mouse, and scrolling in that music PDF does seem to work. 

It was suggested earlier that this may need a video to help show what is actually happening, I do find scrolling with the touch pad is nicer/smoother, but I think that is working as intended. 

Assuming this is just jank, I am removing the releaseblock-stable label for now, if we think we can fix this for a second stable that would be great, but it is not currently clear to me that this qualifies as a stable blocker. 

Unable to reproduce the issue on M51 Build 8172.47.0/51.0.2704.79 - Candy

Hence, changing the Milestone label accordingly.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I sounds, from #21, like this has been fixed? Marking bug as fixed, please re-open if this is still an issue.