Closed
Bug 863176
Opened 12 years ago
Closed 12 years ago
Extra space at the end of a PDF file in the PDF Viewer with high resolution display
Categories
(Firefox :: PDF Viewer, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 826938
Tracking | Status | |
---|---|---|
firefox21 | --- | unaffected |
firefox22 | - | --- |
firefox23 | - | --- |
People
(Reporter: epinal99-bugzilla2, Unassigned)
References
Details
(Keywords: regression)
Attachments
(2 files)
Computer: screen 1920 x 1080 with zoom at 125%
STR:
1) Open a PDF sample like http://excerpts.numilog.com/books/2297001363.pdf
2) Scroll to the end of the PDF
Result:
Observe the unnecessary extra space.
Regression range:
m-c
good=2013-03-14
bad=2013-03-15
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=b672877ed046&tochange=0f7261e288f2
Suspected bug:
Jonathan Kew — bug 844604 - default to auto devPixelsPerPx setting on windows. r=jimm
status-firefox21:
--- → unaffected
tracking-firefox22:
--- → ?
tracking-firefox23:
--- → ?
Keywords: regression,
regressionwindow-wanted
Updated•12 years ago
|
Blocks: 844604
Keywords: regressionwindow-wanted
Comment 1•12 years ago
|
||
Dupe of Bug 826938 ?
Yes, but bug 826938 is about Mac OSX (so the regressed bug is probably earlier in the year).
Comment 3•12 years ago
|
||
The Windows regression is just because we enabled HiDPI support at a later date than on OSX.
Ok, so duped, thanks.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•12 years ago
|
Comment 5•12 years ago
|
||
On highdpi screens we create an extra large canvas and then scale the canvas down with a css transforms to improve the quality. The extra space is due to the handling of the scaling and calculating heights. I'm not exactly sure what the correct handling of this is since IE/Chrome/Firefox all have different results for the attachment (a highdpi screen is NOT needed to see the issues).
As a temporary workaround we can probably wrap the canvas in a div and hide the overflow, but we may want to investigate how this should be properly handled in another bug. I'll look into this tomorrow.
You need to log in
before you can comment on or make changes to this bug.
Description
•