Spurious border-like artifacts in printed output




8 years ago
8 years ago


(Reporter: richard, Unassigned)


Firefox Tracking Flags

(Not tracked)




(1 attachment)



8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0a2) Gecko/20110506 Firefox/5.0a2
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0a2) Gecko/20110506 Firefox/5.0a2

Artifacts that look similar to black top and bottom borders appear around some paragraphs in the print-preview and printed output rendering of the sample page, but not when the page is rendered in the browser.

Reproducible: Always

Steps to Reproduce:
1.Browse to the url above.
2.Choose File>PageSetup and set the page to US Letter, portrait.
3.Choose File>Print.
4.In the print dialog, uncheck Ignore Scaling
5.In the print dialog, check Print Background Colors and Print Background Images.
6.In the print dialog, set all Page Headers and Footers to --blank--
7.In the print dialog, click on the Preview button.

Actual Results:  
On some of the card images, there are black top and bottom borders on the some of the one-line paragraphs.  They seem to occur more frequently on the second page of the output.

Expected Results:  
The printed cards (and the print preview) should match the cards rendered on the page before printing.

Your machine may render the print and print-preview cards on four pages instead of two, with the second and fourth pages containing only two mangled card backgrounds.  That can be corrected by opening about:config and changing the four print.print_margin_XXXX settings from 0.5 to 0.

Aside: The cards are from a page written for a middle school teacher. The ranks mark the student's progress through a reading program. Card selection is driven by a Google spreadsheet.  If anyone needs write access to the spreadsheet let me know, it's a dummy.  The names in the example have been changed to protect the illiterate.

Comment 1

8 years ago
Created attachment 530874 [details]
Screen Shot of part of a Print Preview
You need to log in before you can comment on or make changes to this bug.