Closed Bug 35128 Opened 26 years ago Closed 26 years ago

Pressing "Stop" leaves last rendered page onscreen but unusable

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86
Windows 95
defect

Tracking

()

VERIFIED DUPLICATE of bug 5569

People

(Reporter: danielpeng, Assigned: adamlock)

References

()

Details

(Keywords: testcase)

Attachments

(2 files)

After clicking on a link to "http://bugzilla.mozilla.org/query.cgi" or entering it in the Location box and hitting enter, if I hit "Stop" when the status bar reads "Transferring from bugzilla.mozilla.org" before the last rendered page is cleared, then the previous page is left onscreen, unscrollable, with unusable hyperlinks and nonfunctional animated GIFS. If I then go to a different window and come back, what should be blank in the rendering area instead shows garbage from the other window. I can't reproduce the problem with any other page, but it works every time with this one. Build ID 2000030317 (M14) and 2000033121 (NN6 PR1)
danielpeng@bigfoot.com - thanks for your input, but the correct place for reporting Netscape 6 bugs is http://home.netscape.com/browsers/6/feedback/ index.html. Also, M14 is too old to be reporting bugs against now - it's over a month old, and M15 is due this week. However, if you see this problem in a recent build of Mozilla, feel free to return and ask for this bug to be reopened. Marking INVALID (don't take it personally, there isn't a politer option ;-) Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
This behavior also occurs on 2000040815. I think can give a few more details about the bug now, also. If you hit "Stop" while Mozilla is working on a block of Javascript in <HEAD>...</HEAD>, the rendering area (with the garbage on it from the last page) never gets cleared, but the widgets in it are. The issue doesn't seem to occur with other text in the <HEAD> element. You do need a slow connection to see this behavior (like my 56K modem while downloading the new version of Mozilla at the same time ;-), since you have to catch Mozilla in the act of downloading and parsing the Javascript. Testcase attached.
Keywords: testcase
Reopening, not sure where this should go but I'm looing into it.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
-> Layout
Assignee: asadotzler → troy
Component: Browser-General → Layout
QA Contact: jelwell → petersen
This isn't really layout either. All we do is format and display. It sounds like things were left in sort of a limbo state. I guess that would be either the browser or the web shell's doing
Assignee: troy → don
Component: Layout → XPApps
QA Contact: petersen → paulmac
Sorry for the spam. changing qa contact.
QA Contact: paulmac → sairuh
tever...?
Component: XPApps → Networking
QA Contact: sairuh → tever
Confirming, as several people have seen this. Gerv
Status: UNCONFIRMED → NEW
Ever confirmed: true
Sounds like a docshell problem to me ...
Assignee: don → adamlock
Component: Networking → Embedding: Docshell
QA Contact: tever → adamlock
It works for me. Can you retest with the latest build?
This was a little tricky was I was able to reproduce it with the 2000053108 build on Win98. I think a fast connection on a fast machine makes this difficult to repro. The best bet is to call up the bug in Seamonkey click the attachement link nad then immediately click stop. When I did this the browser content area became totally unresponsive. It stopped repainting and everything although the menus, toolbars, and sidebar still worked.
Status: NEW → RESOLVED
Closed: 26 years ago → 26 years ago
Component: Embedding: Docshell → Event Handling
Resolution: --- → DUPLICATE
OK, I finally managed to reproduce the problem. It looks you're stopped loading just after the old document is thrown away and before the new one has been loaded. At this point, there is no content viewer or document associated with the frame, so there is nothing in it to be rendered. That area is not painted by anyone so what you see as being the old document is actually an unpainted window. You can verify this by dragging some other windows over the frame and observe the trail of crud that gets left behind. We have a longstanding bug for this problem, so I'm marking this as a duplicate of that one. *** This bug has been marked as a duplicate of 5569 ***
Verified duplicate.
Status: RESOLVED → VERIFIED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: