Closed
Bug 1000777
Opened 11 years ago
Closed 11 years ago
pdf.js does not show document if network.cookie.lifetimePolicy is set to 1
Categories
(Firefox :: PDF Viewer, defect)
Tracking
()
VERIFIED
FIXED
Firefox 32
Tracking | Status | |
---|---|---|
firefox32 | --- | verified |
People
(Reporter: Klaus.Malorny, Assigned: Snuffleupagus)
References
Details
(Whiteboard: [pdfjs-c-ff-integration][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4679)
I am using the network.cookie.lifetimePolicy configuration parameter with the value 1 ("prompt for each cookie"). If I then try to view a PDF using the built-in pdf.js, the document space remains empty (dark gray). Number of pages and document properties (via menu) are displayed correctly, however. If I change the configuration parameter back to its default and press reload in the PDF tab, the document is displayed as expected. Turning the value back to 1, the document disappears on reload.
I get the same result on 32 bit windows hourly builds.
Haven't yet tried with a fresh profile, nor found the regression range.
OS: Linux → All
Hardware: x86_64 → x86
On mozilla central (4/15/2014):
last good build:
https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1397567521/
Changeset:
http://hg.mozilla.org/mozilla-central/rev/3d34a3b6443a
First bad build:
https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1397578684/
Changeset:
http://hg.mozilla.org/mozilla-central/rev/d969fb1b3c24
Suspicious:
076498ab4476 Brendan Dahl — Bug 995431 - Update pdf.js to version 1.0.21
Assignee | ||
Comment 3•11 years ago
|
||
It looks like we are hitting bug 365772.
Updated•11 years ago
|
Assignee: nobody → jonas.jenwald
Updated•11 years ago
|
Whiteboard: [pdfjs-c-ff-integration][pdfjs-f-fixed-upstream] https://github.com/mozilla/pdf.js/pull/4679
Comment 4•11 years ago
|
||
Confirmed 31.0a1 (2014-04-28) Win 7 x64
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•11 years ago
|
||
Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 ID:20140430030201 CSet: e19812f56952
Seeing it here too. Lucky that Google found this bug entry, I'd never have thought that cookie settings would have made the difference...
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Depends on: 1007627
Resolution: --- → FIXED
Target Milestone: --- → Firefox 32
Comment 6•11 years ago
|
||
Verified fixed 32.0a1 (2014-05-11), Win 7 x64
Status: RESOLVED → VERIFIED
status-firefox32:
--- → verified
You need to log in
before you can comment on or make changes to this bug.
Description
•