Closed Bug 1079350 Opened 10 years ago Closed 2 years ago

Page down button doesn't scroll PDF downwards

Categories

(Firefox :: PDF Viewer, defect, P4)

32 Branch
x86_64
Windows 8.1
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: martin.stolpe, Unassigned)

Details

(Whiteboard: [pdfjs-c-ux])

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140923175406

Steps to reproduce:

Pressed the page down button multiple times.


Actual results:

When I press the page down button multiple time the page won't scroll down but instead the page will jump between the next page and the current page.


Expected results:

Page should scroll down.
Component: Untriaged → PDF Viewer
We'll try to get some UX input here. We usually try to match the behavior of the browser for various interactions, but here I think it makes more sense that page down goes down a page as it does in any other pdf viewer.
Priority: -- → P4
Whiteboard: [pdfjs-c-ux]
I see this behavior also, usually around Page 3 or 4 of any PDF.  Workaround is either (1) use the mouse and scroll bar to scroll down, or (2) use Adobe Acrobat Reader rather than FireFox's built-in reader to view PDFs.
I know this variant (last seen in 45.5.0esr): If you press "page down" the PDF view toggles between the first part of the first page and the second part of the first page.
I've seen that behavior too.

Oddly enough, both versions seem to happen when running Windows but not on Linux.
It has this behavior on my linux machine (Ubuntu MATE) as well. Here's my run of lsb_release -a.

Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.2 LTS
Release:	16.04
Codename:	xenial

works for me with Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0

Can you still reproduce this bug / behaviour?

Flags: needinfo?(martin.stolpe)
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(martin.stolpe)
Resolution: --- → WORKSFORME

I could not reproduce the bug with some random PDFs in 91.4.1esr either, so it can be assumed to be fixed.

You need to log in before you can comment on or make changes to this bug.