User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 I installed Mozilla 1.6 on a Winxp system, a Win2000 system and a linux system (running Fedora Core 1). When printing from the MSNBC website (http://www.msnbc.msn.com/id/3980466/), selecting print preview creates a 320 page print preview with just a header and footer. Same thing when printing, it just grinds and creates an output with a large number of messed up pages. My printer with the Winxp machines is a HP 1200 and the printer used with the other machines is an HP 8100DN. I really like the new mozilla, but this is a killer on the MSNBC site. If anyone can shed light on this problem, I would appreciate it. Reproducible: Always Steps to Reproduce: 1.Bring up page www.msnbc.msn.com/id/3980466/ 2.Select print preview 3.It will produce a print preview with 320 pages. 4.Exit print preview and select print. It will grind (the progess bar counts very slowly (1%,2%,etc) and then will eventually start printing 320 pages with a header and footer only. Actual Results: Print Preview : 320 pages of just header and footer Printing : 320 pages of just header and footer. Expected Results: Mozilla should have printed the few pages correctly.

Confirming this using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040121 Print Preview shows 316 pages, most of them empty. The actual text is on the last 3 pages, and a part of it is not positioned correctly. Reporter: do you see this problem on Linux? Moving to Browser -> Printing

(In reply to comment #0) Reporting that Mozilla 1.6 exhibits exactly the same behavior on Fedora Core linux.

Setting OS --> All

I can confirm this happens with almost any MSNBC article (at least all of the ones on Slashdot :) from both Firefox 0.8 and Mozilla 1.6 & 1.7b. OS: Windows XP / IBM ThinkPad R32 RAM: 1GB PRINTER: Several different network printers (HPLJ4, HPLJ4000, HPLJ5, etc.)

Dupe of 212984

yep. dupe of bug 212984 *** This bug has been marked as a duplicate of 212984 ***