Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

FIREFOX v 103.00 - MAC OS v10.15.7 - printing PDF directly from Vendor website, the HEADER is messed up

more options

I installed the update for version 103.00. I already followed all the suggested steps of clearing CACHE and cookies and rebooting the system. Did not fix the problem.

I have several Vendors that I connect to their site, login, and print out my Invoice from them. It directly calls the Firefox printer dialogue box and when it is printing directly to any of my HP Printers (as I tried 3 here officejet 8600, Offuce /het Pro 8025e, and HPLaserJet P3100, all did the same thing after applying the 103.00 update.

The 1st page of the document has a different HEADER the remaining pages. It appears that Firefox is not reading interpreting the information about the 1st PAGE Header FONT size or something else correctly on this 1st page, but ONLY on the HEADER. If there is a logo that would normally print, it is completely unrecognizable and not the right size, like it cuts part of it off.

As a workaround, I have had to choose SAVE TO PDF from the Printer Dialog box, and once it is saved as a PDF on my desktop and opened in either Adobe or Preview, it prints correctly.

I have attached a Picture of just the part that is messed up, sorry the rest of the page has account numbers and personal information, and this is more than enough information for you to work with.

This just started happening since I applied the version 103.00. This is definitely a BUG.

I installed the update for version 103.00. I already followed all the suggested steps of clearing CACHE and cookies and rebooting the system. Did not fix the problem. I have several Vendors that I connect to their site, login, and print out my Invoice from them. It directly calls the Firefox printer dialogue box and when it is printing directly to any of my HP Printers (as I tried 3 here officejet 8600, Offuce /het Pro 8025e, and HPLaserJet P3100, all did the same thing after applying the 103.00 update. The 1st page of the document has a different HEADER the remaining pages. It appears that Firefox is not reading interpreting the information about the 1st PAGE Header FONT size or something else correctly on this 1st page, but ONLY on the HEADER. If there is a logo that would normally print, it is completely unrecognizable and not the right size, like it cuts part of it off. As a workaround, I have had to choose SAVE TO PDF from the Printer Dialog box, and once it is saved as a PDF on my desktop and opened in either Adobe or Preview, it prints correctly. I have attached a Picture of just the part that is messed up, sorry the rest of the page has account numbers and personal information, and this is more than enough information for you to work with. This just started happening since I applied the version 103.00. This is definitely a BUG.
Capturas de pantalla adjuntas

Todas las respuestas (9)

more options

Thank you for your report and screenshot.

Can you tell whether you were printing a web page or a PDF? A PDF normally would display in Firefox's built-in PDF viewer with its distinctive controls. It also has a very different context menu (right-click or Ctrl+click).

Another Mac user reported a similar problem: https://support.mozilla.org/questions/1384467

(You can see I'm a little confused there about printing a PDF or printing to a PDF...)

more options

I believe it is creating a PDF from within Firefox, as it opens up a NEW tab. then I click on the Printer icon on the upper left within the firefox browser. Firefox is definitely creating the PDF because there is a PDF is downloads. I just logged into the webpage again, told it to print the document. It definitely is creating it's own PDF and puts it in downloads. Regardless if I tell it to print from the pdf in downloads to either the firefox printer dialogue box, or tell it to print from the system printer dialogue box, it does the same thing. Apparently Firefox pdf creator has an issue. But, from MAC on the Printer Dialogue box, where you can choose the printer you want it to print to, If I choose SAVE PDF, and save this on the Desktop, and then open that PDF with Preview or ADOBE and tell it to print the 1st page is fine. it only does it when the 1st page HEADER is different. Much like printing a company letter head page on a multiple page letter, where the 1st page header is different than the remaining pages header.

This is very broken in v 103.00

Hopefully they can fix this soon, because by next month, I will have to go through the additional steps to get these things to print correctly.

more options

Also, from within Firefox, if I click on downloads, and open up the PDF that it created, and instead of printing, I click on the download button, and save a copy on my desktop. Then I open in Preview or Adobe, it prints correctly. Firefox is generating the PDF correctly, but when it opens it to print, it is having a serious issue with one or more of the PDF control codes.

more options

Also after reading the other link you provided, the heading on the sample I provided does have a QR code on it. But if I open up the PDF that Firefox creates with Preview or Adobe, it prints fine from those apps, just not from Firefox even though it displays correctly on the screen, and in the preview on the printer dialogue box.

more options

Aha, if the PDF is on the downloads list as a PDF, I would be pretty sure the site is pushing the PDF to Firefox in that format. They do that to control the layout because every browser prints a page slightly differently, not to mention the effects of add-ons and other blockers. The only time Firefox creates a PDF on its own is when you select the "Save to PDF" "destination" in the print dialog.

I think for now this might be best:

(1) Click the print button in the site and wait for Firefox to download the PDF and open it in a new tab (2) Ignore or close the new tab (3) Open the Downloads list and right-click (or Ctrl+click) the PDF, and click "Open in [external PDF app]"

For all I know, this bug is already on file, but if you happen to find a public PDF that causes the problem, that would be helpful so we can give the developers a file that doesn't contain personal information.

more options

I am having the same issue with printing pdfs from the FF pdf preview window. The problem persists when using the printer icon and selecting Save to pdf. Using the Download icon circumvents the problem and allows the saved file to print correctly.

Printing from the FF pdf viewer is not functioning properly for pdfs with images embedded.

more options

jscher2000 - Support Volunteer said

Aha, if the PDF is on the downloads list as a PDF, I would be pretty sure the site is pushing the PDF to Firefox in that format. They do that to control the layout because every browser prints a page slightly differently, not to mention the effects of add-ons and other blockers. The only time Firefox creates a PDF on its own is when you select the "Save to PDF" "destination" in the print dialog. I think for now this might be best: (1) Click the print button in the site and wait for Firefox to download the PDF and open it in a new tab (2) Ignore or close the new tab (3) Open the Downloads list and right-click (or Ctrl+click) the PDF, and click "Open in [external PDF app]" For all I know, this bug is already on file, but if you happen to find a public PDF that causes the problem, that would be helpful so we can give the developers a file that doesn't contain personal information.

https://www.sowela.edu/wp-content/uploads/How-to-search-for-PDF-files-in-folders.pdf

more options

jscher2000, I tried to post a link to a public pdf doc but it got blocked so I sent you a DM.

more options

gschertz said

jscher2000, I tried to post a link to a public pdf doc but it got blocked so I sent you a DM.

Thank you, a moderator should be able to release your post.

There is a bug on file and it turns out to be a Mac only issue, caused by fixing a different issue. I've referenced both of your threads and asked the developers whether there are any workarounds. Otherwise, we might be waiting a month for the fix.