You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When scrolling a lager PDF with the mouse (especially with smaller wheel spin) the scrolling behavoiur with it's bouncing is quite annoying.
As you can see here in this animation you even get stuck sometimes on the same place (e.g. at page break):
To Reproduce
I'm taking a fileBase64Decoded PDF but this shouldn't matter though. It just needs to be multiple pages.
I tried playing around a bit with pageSnapping and the physics but there was no real satisfiying result.
Maybe it would also be worth a try to implement it's own ScrollController to kinda control the scroll behaviour on your own. But it seems like this whole scrolling stuff is somewhere deep in related packages like photo_view_gallery.
I would like to push resolution of this issue 🙏 I like the library but this bounding behaviour while viewing PDF will probably make me search for another library if not resolved soon.
Describe the bug

When scrolling a lager PDF with the mouse (especially with smaller wheel spin) the scrolling behavoiur with it's bouncing is quite annoying.
As you can see here in this animation you even get stuck sometimes on the same place (e.g. at page break):
To Reproduce
I'm taking a
fileBase64Decoded
PDF but this shouldn't matter though. It just needs to be multiple pages.I tried playing around a bit with
pageSnapping
and thephysics
but there was no real satisfiying result.Behaviour is same in Chrome and Edge.
Expected behavior
pageSnapping: false
should actually not pageSnapOR
Based on the given ScrollPhysics an according scrolling behaviour, e.g.
BouncingScrollPhysics
RangeMaintainingScrollPhysics
OR
it would actually be nice to have a scrollbar available, like already mentioned in #81.
The text was updated successfully, but these errors were encountered: