Closed Bug 270283 Opened 20 years ago Closed 19 years ago

Does not print background colors even though turned on in options

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: tmorrisey, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 When printing pages at http://home.cfl.rr.com/troop240/Calendar.htm, the background color does not print. I open it in IE and can print with background colors Reproducible: Always Steps to Reproduce: 1. Go to http://home.cfl.rr.com/troop240/Calendar.htm 2. Print Preview and adjust size to fit 1 page 3. Print Actual Results: Prints the calendar without all the Month and Day information around the calendar Expected Results: Printed with a blue background frame around caledar. Lettering is white. Without the background color you have white text on white paper
I believe this is the same bug that affects maps.google.com Example page http://maps.google.com/maps?q=from%207719%2016th%20Ave%20NE%2C%20Seattle%2C%20WA%2098115%20to%2012th%20Ave%20and%2042nd%2C%20seattle When printing these directions, the path from the destination and starting place is not shown. Also not shown in print previw, happens regardless of background image printing on or off.
On second thought, perhaps the problem with maps.google.com is a separate bug, my version of Firefox does not have the same problem the reported notices, but does exhibit the problem on maps.google.com Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
This is also happening on my linux firefox: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 When I do a print preview or print of a page with backgound images/colors, they show as white.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.