Closed
Bug 829737
Opened 11 years ago
Closed 9 years ago
Progress spinner while loading a PDF is not visible
Categories
(Firefox :: PDF Viewer, defect, P3)
Tracking
()
RESOLVED
FIXED
Firefox 36
People
(Reporter: kats, Unassigned)
References
Details
(Whiteboard: [pdfjs-c-ux][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4150)
When loading http://www.restaurant.org/foodhealthyliving/fluinfo/handwashing/handwashing_poster.pdf in my FF window sized to 1439x801, it displays a progress spinner. However, the spinner is positioned halfway down the first page of the PDF, which means it's out of sight and I have to scroll down to actually see it. It's also pretty subtly coloured so I scrolled up and down a few times thinking it was a blank PDF before I noticed the spinner going. Expected results: the spinner is positioned in the middle of *visible area* of the page so that you don't have to scroll anywhere to realize that the PDF is still loading.
Comment 1•11 years ago
|
||
If the initial Rendering would use "Page Fit" instead "Automatic Zoom" this would be a non-Issue, no?
OS: Mac OS X → All
Reporter | ||
Comment 2•11 years ago
|
||
If that does what it sounds like, then yes, that should take care of this.
Updated•11 years ago
|
Priority: -- → P3
Whiteboard: [pdfjs-c-ux]
Updated•10 years ago
|
Whiteboard: [pdfjs-c-ux] → [pdfjs-c-ux] https://github.com/mozilla/pdf.js/pull/4150
I just filed bug 1013312 which is a genuine dup of this and wanted to point out that in my scenario defaulting to "page fit" does not resolve this issue. I had set the zoom to "page width" and then scrolled to the bottom. The spinner is placed in the center of the page and not our view of the page, so it was not visible.
Updated•10 years ago
|
Whiteboard: [pdfjs-c-ux] https://github.com/mozilla/pdf.js/pull/4150 → [pdfjs-c-ux][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4150
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 1084158
Resolution: --- → FIXED
Target Milestone: --- → Firefox 36
You need to log in
before you can comment on or make changes to this bug.
Description
•