New issue
Advanced search Search tips

Issue 707757 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 695907
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-04-20
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

The PDF viewer scrolls too fast for comfort

Reported by smith.ni...@gmail.com, Apr 3 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Use Chromium on a macbook pro
2. Open a PDF
3. Scroll

What is the expected behavior?
Dear Chromium Team,

In Google Chrome, the pdf scroll speed feels natural.  In Chromium the speed feels like it is moving too quickly, making scrolling uncomfortable. 

What went wrong?
Sometimes the pdf scrolls further than expected.  It is not a mouse sensitivity issue, it only happens in Chromium.  It feels like the acceleration, or the scaling factor of the mouse scroll event is off in some way.

Did this work before? N/A 

Chrome version: 57.0.2987.133  Channel: stable
OS Version: OS X 10.12.4
Flash Version: 

Could you please take the speed down a notch or two?   If not I would be happy to settle for knowing which flag to set if that is possible?
 
Labels: Needs-Triage-M57

Comment 2 by sdy@chromium.org, Apr 4 2017

Components: -UI Internals>Plugins>PDF
Components: Blink>Scroll
Are Chromium and Google Chrome the same version? I can't think of anything off the top of my head to account for this behavior difference.

Where did you get Chromium from?
Labels: Needs-Feedback
NextAction: 2017-04-20
Could you tell us what version of chromium you were using? This looks like you are reporting this from an official version of chrome.

The version of chromium that you don't download via (https://download-chromium.appspot.com/) doesn't autoupdate. So it will be the version that you downloaded whenever. We did have an issue like this in the past and I wonder if the issue is that you are using an old version of chromium that has the old bug (specifically  issue 604734 )


smith....@ still awaiting feedback. We believe this is fixed in that you could be using an old version of chromium
I am using  57.0.2987.133 (64-bit)

It is the version packaged in the FreeSMUG distribution of Chromium.
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 14 2017

Cc: dtapu...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: wjmaclean@chromium.org
I can certainly repro it with that distro. It works correctly when you enable out of process iframes via chrome://flags

Certainly something related to the event resending.

James any idea? Could there be build config differences between this FreeSMUG distro and what we use for release chrome? Or finch configs?
Mergedinto: 695907
Status: Duplicate (was: Unconfirmed)
This sounds to me like a dup of https://bugs.chromium.org/p/chromium/issues/detail?id=695907

The fix for this was landed in M59, and merged back to M58, but would likely still affect M57 as per this report.

Although PDF doesn't use OOPIFs, enabling them may have forced mouse wheels to be directly routed to the guest process, thus avoiding a resending issue.
Just confirming it's fixed in the current FreeSMUG Chromium distro.  Sincere thank you to everyone involved.

Sign in to add a comment