Closed Bug 1300525 Opened 5 years ago Closed 2 months ago
After selecting a zoom level, navigation keys scroll through zoom levels, not through pages
[Affected versions]: - latest Nightly 51.0a1 (2016-09-04) - latest Aurora 50.0a2 (2016-09-04) - 49.0b10 build1 (20160902105049) - 48.0.2 build1 (20160823121617) [Affected platforms]: - Windows 10 x64 - Windows 8.1 x64 - Ubuntu 14.04 x86 [Steps to reproduce]: 1. Launch Firefox 2. Open a random .pdf file, using pdf.js (e.g. http://www.pdf995.com/samples/pdf.pdf) 3. Click the Zoom control in order to open the zoom level list and select a random level 4. Try to scroll the document pressing the "down" and "up", "right" and "left", "Page Down" and "Page Up", "End" and "Home" keys from the keyboard [Expected result]: - The user is able to scroll the .pdf document, even if the zoom level control was previously used [Actual result]: - The "down" and "up", "right" and "left", "Page Down" and "Page Up", "End" and "Home" keys are switching the zoom levels (and they are applied to the document) until a random area of the document is clicked - The fact that the zoom level control remains selected is not visible on Windows (on Ubuntu it is highlighted by dotted edges) [Regression range]: - I will investigate this as soon as possible [Additional notes]: - This issue seems to have the same cause like Bug 836732 - On Mac OS X zoom level button remains selected, but the zoom level selection list is open when navigation keys are used - a less confusing case
5 years ago
Summary: After selecting a zoom level, navigation keys scroll through pdf levels, not through pages → After selecting a zoom level, navigation keys scroll through zoom levels, not through pages
Too late for a fix for 49, but we could still potentially fix this for 51 or 50.
Could this be fixed by after clicking on the zoom and selecting the zoom level we set the focus back to the pdf space, this be done by simulating a click on the area?
Also having a regression range is likely not possible as the other bug linked here Bug 836732 has a comment about this behavior happening in Firefox 16. my guess is that it is likely always to have been present.
Brendan, do you have time to investigate here?
When did this behavior change? As far as I know, this is how it has always been.
Iulia, please see comment 5.
(In reply to Brendan Dahl [:bdahl] from comment #5) > When did this behavior change? As far as I know, this is how it has always > been. Hello! Yes, you are right, Firefox always had this behavior (all the way back to Firefox 19, when the built-in PDF viewer was introduced).
5 years ago
Status: NEW → RESOLVED
Closed: 2 months ago
Depends on: 1715638
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.