No possibility to print PDF online invoices by Firefox PDF Viewer

UNCONFIRMED
Unassigned

Status

()

Firefox
PDF Viewer
P3
normal
UNCONFIRMED
5 years ago
4 years ago

People

(Reporter: Sören Hentzschel, Unassigned)

Tracking

19 Branch
x86
All
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [pdfjs-c-other][pdfjs-f-need-info])

(Reporter)

Description

5 years ago
PDF-online invoices which are downloaded from TELEKOM Germany
or from DiBa-Bank are shown by the internal Firefox PDF Viewer. But it is not possible to print those documents. The print preview shows an empty side. When you now have pressed the print button of the printer window, the next windows (“print”) is showing the transfer of the data to the printer till the value of 100%. But the process stops now. The print order report says that this order is in the waiting loop.
I tested this with a Telekom invoice and could not reproduce the issue with Firefox19 and Firefox trunk. One umlaut issue in Firefox19 was already fixed in the trunk build but printing worked as expected in both versions.
Is there a sample pdf you could share that exhibits this behavior so we can test it?
Flags: needinfo?(cadeyrn)
Priority: -- → P3
Whiteboard: [pdfjs-c-other][pdfjs-f-need-info]

Comment 3

5 years ago
I don´t want to sent my Telekom Germany invoice because of data protection. But fact is: I can print all downloaded PDFs ( from shops, banks .... ) with exeption of the Telekom PDF. Here is Windows XP prof. SP3; Firefox 19.02.
I would send Brendan my Telekom invoice but I can not reproduce any printing issues with it :-(

Is that a normal Telekom monthly invoice for a Telekom landline that you are trying to print ?

Comment 5

5 years ago
@ Matthias: It is an monthly invoice from T-Mobile which was send by E-Mail as enclosure. I could open it but I could not print it.

@Brendan: I´ll  try to forward the E-Mail with the enclosed invoice to your
E-Mail address. Pls. handle it confidential.
(Reporter)

Updated

4 years ago
Flags: needinfo?(cadeyrn)
You need to log in before you can comment on or make changes to this bug.