Closed
Bug 178366
Opened 22 years ago
Closed 20 years ago
Mozilla doesn't complete loading a page.
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Core
DOM: UI Events & Focus Handling
Tracking
()
RESOLVED
DUPLICATE
of bug 143398
People
(Reporter: gf_bugz, Assigned: saari)
References
()
Details
(Keywords: hang)
When you have an "onload" event that updates the src for an iframe it loads the page fine, but the throbber never stops spinning, there are no messages in Javascript console and pressing the Stop button produces no effect. If I open the same page outside of the frameset it loads fine and completes the load. (try: http://www.gena01.com/mozilla/frames/iframe.html ) but inside the frameset it never stops loading. I am currently using/seeing this in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021029 Phoenix/0.4
Comment 1•22 years ago
|
||
I'm seeing this in trunk builds 2002102508 on Mac OS X and 2002110408 GNU/Linux.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•22 years ago
|
||
Moving to Event Handling component since the behavior evaporates if the onload handler is not specified. However, the problem is not present if the page is loaded by itself, so it could be a problem in framesets.
Comment 3•22 years ago
|
||
WFM with 1.2 (20021126). reassigning to component owner. reporter: can you reproduce this bug with a recent build of mozilla?
Assignee: asa → saari
QA Contact: asa → rakeshmishra
Reporter | ||
Comment 4•22 years ago
|
||
It's still there, it still doesn't stop loading, maybe i wasn't clear with the URLs in my comments. When I open http://www.gena01.com/mozilla/frames/ it's spinning and I can't stop it. Pressing stop button has no effect. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021201 Phoenix/0.4
Comment 5•20 years ago
|
||
*** This bug has been marked as a duplicate of 143398 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•