Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox 6.0 improperly prints a web page. Please fix.

more options

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.

모든 댓글 (1)

more options

The problem still exists in Firefox 7.0.

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