Closed Bug 109778 Opened 23 years ago Closed 21 years ago

After printing page, print does not work until restarting Netscape

Categories

(Core :: Printing: Output, defect)

Product:
Core
Component:
Printing: Output
Platform:
HP
HP-UX
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: BarrettLndstrm, Assigned: shannond)

References

(
URL
)

Details

This is part of mozilla's printing test case. Test steps: 1. Start Browser and go to http://sportsillustrated.cnn.com/ . 2. Print the page. 3. Go to any other web page. 4. Print the page. The first page never actually prints at all. And at step four the system just beeps at you (if sound is working on your hpux box). This behaviour stays this way until you restart the browser. I could not reproduce this on linux using the 6.2 RTM build.
qa to me, and adding blocker bug
Blocks: 18687
QA Contact: sujay → barrettl
Looks like this is only on the branch ... trunk doesn't have this bug.
I just tried this and it seems to work for me.. I have the 11/13 build on my Dell box and I can print that SI page and then print another page after it..I get both printouts...
Dell box? I assume that you are running windows then. This bug is HPUX specific.
On a similar note we're also finding that some pages don't print at all ... same behavior as the http://sportsillustrated.cnn.com/ page except the page doesn't print but then still allows other pages to print. One of these pages seems to be www.aol.com and the printing frame tests on mozilla.org: http://www.mozilla.org/quality/browser/front-end/testcases/printing/frames.html The mozilla.org frame tests print fine when you select to print "Each frame separately" however do not print at all when you select to print them "As laid out on the screen" None of these problems show up on the recent HPUX trunk builds, however, only on this build from the 0.9.4 branch.
I can't reproduce this problem. The sample URL prints fine and I can still produce other printouts from the same mozilla instance. The previous comment implies this problem was specific to the 0.9.4 branch. I'm going to resolve this.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.