Hello,

I have managed to reproduce some faulty behaviors in 104.0a1 (2022-07-03) in Ubuntu 22 , Windows 10 and macOS 11.6.6 using the following printers:

• Phaser 3020
• HP OfficeJet 6950
• HP DeskJet 3720
• Canon TS3451

I have used the attached document from this ticket , as well as the document used in bug 1252240 and unveiled somewhat similar behaviors as the attached ones.

I have searched for a regression and uncovered the following pushlog_url from which it seems that the culprit would be 1772225.

Here you can see the faulty behaviors encountered on the aforementioned configurations

(In reply to Vlad Lucaci, QA (:vlucaci) from comment #4)

Hello,

I have managed to reproduce some faulty behaviors in 104.0a1 (2022-07-03) in Ubuntu 22 , Windows 10 and macOS 11.6.6 using the following printers:

• Phaser 3020
• HP OfficeJet 6950
• HP DeskJet 3720
• Canon TS3451

I have used the attached document from this ticket , as well as the document used in bug 1252240 and unveiled somewhat similar behaviors as the attached ones.

I have searched for a regression and uncovered the following pushlog_url from which it seems that the culprit would be 1772225.

Here you can see the faulty behaviors encountered on the aforementioned configurations

Which OS did you use to find the regression range?
Since the range is newer than this bug, maybe this bug was fixed in the past and regressed again. Could you try to find a fix in the range 2016-02-29 (which is when this bug was filed) to 2022-06-26 (which is a day before the push you mentioned)?

Hello Marco,

The first regression range was pulled using macOS 11.6.6.

I have tried to find a fix in the range of 2016-02-29 and 2022-06-26 (on Windows 11) but the bisection stops giving builds previous to 2016-03-01.
Here is the regression I pulled while trying to find the fix, maybe there is something useful in here.

I have tried to manually download a build from archive/mozilla from 2016-02-29 and reproduce the issue, but the builds from that period only display an infinite loading when trying to access any link.

Jonathan, you might want to have a look since it seems somehow related to bug 1772225's fix.

Vlad, it's not clear to me what "bad" output comes from what system/configuration. It would be most helpful if you could attach images here, with comments that explain what each one is.

Comment 4 mentions "faulty behaviors in [...] Ubuntu 22 , Windows 10 and macOS 11.6.6", which cannot all be related to bug 1772225 because that bug only touched Mac-specific code. So any problems on other platforms must be a separate issue (perhaps bug 1774631?).

I can identify one specific issue here: Trying the example here in attachment 8724920 [details] on macOS with my HP LaserJet printer, I see an overall improvement in the print quality when bug 1772225 landed, as it went from being a blurry rasterized image to a sharper, clearly vector-based output. However, the logo with the three trees at the top left of the page is mishandled (printed at the wrong scale) such that only the top-left part of it shows, the rest is clipped away. This matches what I see in Vlad's IMG_20220704_120105.jpg, and no doubt relates to bug 1772225, so we should look into that.

(In reply to Jonathan Kew (:jfkthame) from comment #8)

Vlad, it's not clear to me what "bad" output comes from what system/configuration. It would be most helpful if you could attach images here, with comments that explain what each one is.

Comment 4 mentions "faulty behaviors in [...] Ubuntu 22 , Windows 10 and macOS 11.6.6", which cannot all be related to bug 1772225 because that bug only touched Mac-specific code. So any problems on other platforms must be a separate issue (perhaps bug 1774631?).

Vlad, needinfo for the questions above.

I can identify one specific issue here: Trying the example here in attachment 8724920 [details] on macOS with my HP LaserJet printer, I see an overall improvement in the print quality when bug 1772225 landed, as it went from being a blurry rasterized image to a sharper, clearly vector-based output. However, the logo with the three trees at the top left of the page is mishandled (printed at the wrong scale) such that only the top-left part of it shows, the rest is clipped away. This matches what I see in Vlad's IMG_20220704_120105.jpg, and no doubt relates to bug 1772225, so we should look into that.

Vlad, could you file a new bug for this regression, and mark it as "Regressed By" bug 1772225?

Better to track everything in separate bugs, otherwise it will get pretty confusing pretty fast.

Hello,

• For the three trees issue that only affects the macOS platform, a separate ticket has been filled : 1779202 as per requested in comment 9.

• This attachment was for the print job done on Windows 10x64 with HP OfficeJet 6950 - The title for the PDF document is very coarse and full of artifacts

-This attachment was for the print job done on Ubuntu 22 with HP DeskJet 3720 - The title displays the same behavior(not as obvious) as for Windows 10 print job.

Should I create a different ticket for the Windows and Ubuntu print job behaviors?

OK, I think the printing improved since this bug was filed, but it is still not good.

(In reply to Vlad Lucaci, QA (:vlucaci) from comment #10)

• For the three trees issue that only affects the macOS platform, a separate ticket has been filled : 1779202 as per requested in comment 9.

Thanks!

• This attachment was for the print job done on Windows 10x64 with HP OfficeJet 6950 - The title for the PDF document is very coarse and full of artifacts

-This attachment was for the print job done on Ubuntu 22 with HP DeskJet 3720 - The title displays the same behavior(not as obvious) as for Windows 10 print job.

Should I create a different ticket for the Windows and Ubuntu print job behaviors?

I don't think so, we can probably consider this to be the same problem as originally filed (unless it looked good at some point and regressed again).
Maybe you could check on a build from a few months ago (before bug 1774631) and see if you can still reproduce.

Three notes:

(In reply to Marco Castelluccio [:marco] (back Aug 22) from comment #11)

• This attachment was for the print job done on Windows 10x64 with HP OfficeJet 6950 - The title for the PDF document is very coarse and full of artifacts
  [...]
  Should I create a different ticket for the Windows and Ubuntu print job behaviors?

I don't think so, we can probably consider this to be the same problem as originally filed (unless it looked good at some point and regressed again).

Note #1: I disagree that it's the same problem, and tend to think we should file a new bug. Vlad's photographed Windows behavior (with the title looking coarse, with lines/jaggies extending from characters a bit) looks hugely better than the screenshots that the original reporter attached here, which have a ton of bizarre corruption covering up the whole top area of the page. So I suspect there's a different root issue there, and the original issue went away at some point (maybe with a PDF.js update), and we don't see badness like the original photos at this point.

Note #2: comment 10's "Ubuntu 22" link seems have been mis-pasted -- it's the same URL as the macOS link in that comment (and it does seem to be a photo of bug 1779202). Not sure if we have a photo of Ubuntu 22.04 rendering, but it sounds like it's similar to the windows photo (maybe it's the second page shown in that photo.

Note #3: I'm actually on Ubuntu 22.04 myself, and I tried printing the first page to my own local printer (a Brother HL-2280DW) with today's Nightly as well as Nightly 2022-06-26 -- and for me, it prints just fine, with no jaggies like the ones that were shown in Vlad's Windows photo. (There are very minor flecks around the characters, but those seem to be shown in all PDF viewers that I've tried and seem to be part of the "rustic" style of the font/design that's used in the PDF here.)

I just tested on Windows and I can reproduce the coarse "title jaggies" that Vlad's photo showed -- but I can reproduce that in Edge and Chrome as well when printing the same original PDF (see photo), so that seems to not be a Firefox-specific issue. Likely a low-level Windows graphics or font-rendering bug of some sort.

So: I think we don't really need to track that as a Firefox bug.

So I think we can close this as WORKSFORME in terms of the original bug report here, since we aren't seeing anything anywhere near as bad as the original reporter's attached photos.

And for issues in current Firefox releases:

• The macOS-specific issue is tracked in bug 1779202.
• The Windows-specific issue seems to be a Windows bug (affecting all major browsers available on Windows) and not a Firefox bug.
• On Ubuntu, it's not entirely clear whether there are issues or not, per my last two notes in comment 12 (I'm not sure if we have a photo right now, and I'm not seeing any issues myself when printing this PDF on Ubuntu 22.04)

Vlad, would you mind retesting on Ubuntu, to see if you're still seeing any substantial corruption/issues there (aside from the small "flecks" that show up on-screen as well)?

If you do, please file a new bug on those with a photo to show what the issues look like there. Thanks!

Hello,

Sorry for the late response.

Confirming that no substantial corruption/issues are displayed on Ubuntu 22 print jobs using Canon TS3400 Serios Inkjet Printer.

The three trees logo is properly displayed.