We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

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 6.0 improperly prints a web page. Please fix.

  • 1 பதிலளி
  • 8 இந்த பிரச்னைகள் உள்ளது
  • 5 views
  • Last reply by Steve Chessin

This is on a MacBookPro running MacOS 10.5.8.

Go to http://www.green960.com/pages/lineup.html Click on the first "Print article", just under "listen live". When the Print dialogue pops up, select Preview. The first page shown is almost all blank, the second page shows the last two programs.

Now do the same in Safari. (You'll have to select "Open PDF in Preview" from the PDF menu.) The first page shows the first five shows, and the second page shows the next three.

(The second "Print article", the one just above "Weekend Programs", works fine.)

I can workaround the problem *for this page* by ignoring the "Print article" links and using the Firefox Print button, but it'd really be nice if someone fixed the bug, as I've seen similar behavior before.

This is on a MacBookPro running MacOS 10.5.8. Go to http://www.green960.com/pages/lineup.html Click on the first "Print article", just under "listen live". When the Print dialogue pops up, select Preview. The first page shown is almost all blank, the second page shows the last two programs. Now do the same in Safari. (You'll have to select "Open PDF in Preview" from the PDF menu.) The first page shows the first five shows, and the second page shows the next three. (The second "Print article", the one just above "Weekend Programs", works fine.) I can workaround the problem *for this page* by ignoring the "Print article" links and using the Firefox Print button, but it'd really be nice if someone fixed the bug, as I've seen similar behavior before.

All Replies (1)

The problem still exists in Firefox 7.0.

How do I turn this forum question into a bug report?