299303 - Printing & Preview: Background colors bleed outside of box to entire page.

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Douglas Moyes]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

My Online C Crash Course at
http://www.stellimare.com/~aragorn/scouting/mb/computers/c-cc.html displays as
expected in the browser, but, when printing with background colors on, the
background color of the <pre> elements bleed over to the entire page. The first
page will print normally, but the others do not.

This problem exists on all platforms, Max OS X, Windows, and Linux. It can also
be seen in the print preview. 

Reproducible: Always

Steps to Reproduce:
1. Open the page at http://www.lds.org/library/display/0,4945,2043-1-3098-1,00.html
2. Go to page setup, check "Print Background (color & iamges)"
3. Either print, or view the page in print preview.

Actual Results:  
First page prints as expected.  Following pages with <pre> elements have the
<pre> tags background color bled over the entire page, and not contained within
the boxed in section as on the first page, and as the browser normally displays it.

And burns lots of toner...

Expected Results:  
Printed the page just as it looks in the browser (not in the print preview).

Comment 1

[zug_treno]

Related to Core bug 239756?

Comment 2

[John P Baker]

duplicate of bug 294836 ?

Comment 3

[Philip Withnall (unavailable)]

This happens for me, too, except it's with a table.

Comment 4

[rcampbel]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060123 Firefox/1.5.0.1  Windows XP SP2

Ink consumption, particularly colored ink, can be a burden to people or businesses that print from Firefox regularly.  If the browser creates unnecessary ink/toner usage, it increases the cost of using the browser.

Procedures ::

1) Left click on the following link :: http://www.stellimare.com/~aragorn/scouting/mb/computers/c-cc.html
2) File->Page Setup, check the Print Background option.
3) File->Print Preview...
4) Look at page six
5) Close print preview and view last segment of linked website

Results ::

The blue box's fill color spills out to the bottom of the print preview page, while it is contained in the box on the website.

Expected Results ::

The blue box's fill color to be contained to the box on both the website, print preview, and the printed document.

Reproducible: Always

Comment 5

[Mark Clements]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4


I had the same problem with a table.  The interesting thing is that the table cell background spilled out onto the entire page, IF the cell with a background colour was on the first row.  Otherwise the page was fine (i.e. coloured backgrounds within the table but not on the first row were fine).

It appears that Firefox is taking the background settings for the first element it on the printed page as the background settings for the page itself, rather than using the background settings for the body, as expected.

Note that this was using background images, rather than colours, so it seems as if all background related settings are overflowing, not just colour.

Comment 6

[Steve Grecni]

I can confirm this is happening for me using css background colors.

Comment 7

[Wayne Mery (:wsmwk)]

(this link is NA http://www.stellimare.com/~aragorn/scouting/mb/computers/c-cc.html )

I tested http://www.lds.org/library/display/0,4945,2043-1-3098-1,00.html - not sure I see what you did when I used trunk build 

Is this still a problem for you using a trunk build?
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ 

Comment 8

[Steve England [:stevee]]

No response from reporter re: comment 7 -->INCOMPLETE.
Reporter, if you still see this problem with the latest Firefox 2 please reopen this bug. Thanks!

Comment 9

[Mark Clements]

I've re-tested this on 2.0.0.4 and can't duplicate the problem.  It seems to be fixed, as far as I'm concerned.