Closed Bug 200861 Opened 23 years ago Closed 21 years ago

Several lines near the bottom of the article text are missing when printed

Categories

(Core :: Printing: Output, defect)

x86
Windows 98
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: cheljuba, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 If this article remains as it is currently, it contains a paragraph beginning "Highs on Saturday ..." When printed, a big chunk of text is missing from mid sentence. I've noticed this happens with many CNN articles, and with Netscape 7.02 as well. I'm printing to an HP laserjet 2100. It doesn't matter which driver (PCL 5, PCL 6, Postscript) I use -- all exhibit the problem. Reproducible: Always Steps to Reproduce: 1.load and print the page 2. 3. Actual Results: Partial printout of the article Expected Results: Complete printout This is a fresh, initial install of Mozilla. I was hoping it would not exhibit the same problem I had seen (and reported weeks ago) in Netscape.
WFM, WinXP 2003040504 HP Deskjet 600
I have seen a similar lost-lines problem on Moz 1.4 and have just recreated it on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030812. When I printed http://www.february-7.com/features/conan.htm, a line was lost after the breaks between the second to third page and the third to fourth page. No lines were lost between the first and second pages. The print preview was missing lines in exactly the same two places. I ran the tests using two different printers, an IBM 4029 laser printer and an HP DeskJet 722C. Although the pages were formatted differently for the two, causing a different number of lines per page, in each case the results were the same: No lines lost between pages 1->2, but lines were lost between pages 2->3 and 3->4. Different lines were lost for each printer because the breaks were at different places in the text.
The URL given in this report is no longer valid. Can you give another example URL, or better yet a test case, that demonstrates this bug? Need to see if this could be related in any way to bug 216195 or bug 220102
Since there's been no response to comment 3, and since the issue in comment 2 is now being covered in bug 216195, I am closing this bug. Feel free to reopen it if you merely provide another CNN URL where this bug occurs.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.