Closed
Bug 47279
Opened 24 years ago
Closed 24 years ago
Mozilla goes into a loop with only one frame when two was specified.
Categories
(Core :: Layout: Images, Video, and HTML Frames, defect, P3)
Core
Layout: Images, Video, and HTML Frames
Tracking
()
People
(Reporter: joesv59, Assigned: pollmann)
References
()
Details
(Keywords: crash)
Trying to retrieve that page results in a neverending loop. With Mozilla/Solaris the repeated message is "Error getting url widget service: TypeError: Components.classes[progid] has no properties". With Mozilla/NT it is "Enabling Quirk stylesheet".
Comment 1•24 years ago
|
||
Confirmed on linux 2000080108 with the loop message "Error getting url widget service: TypeError: Components.classes[progid] has no properties". Changing OS/Platform to All. Requesting the reporter try to create a simplified testcase.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Solaris → All
Hardware: Sun → All
Also confirmed on 2000080120 on Linux. However, the error about "Components.classes[progid] has no properties" may not be relevant, since every single page you load comes with this error (and this error started showing up a couple of weeks ago).
More info. When I visited this site with Lynx, I saw a trace of what is happening. The page contains a frame http://www.nasslan.net/kampanj/, which has the html code: Server: Apache/1.3.12 (Unix) PHP/4.0.1pl2 Connection: close Content-Type: text/html <html> <body onload="window.location='http://www.nasslan.net/kampanj/index.php';"> </body> </html> When I put the above code into a local file and load it, then it seems to work.
Reporter | ||
Comment 4•24 years ago
|
||
Now I am using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20000728 and gets "*** check number of frames in content area" instead. This seems to do it: <html> <head> <title>Hej</title> </head> <frameset frameborder=0 framespacing=0 border=0 rows=100%,*> <frame name=frame src=http://www.nasslan.net/kampanj/> </frameset> <noframes> <body> Hopp </body> </noframes> </html> Changing nasslan.net to something else does not give the error. Loading the nesslan-page directly does not either. But is it the same error?
Comment 5•24 years ago
|
||
This seems to be related to frames. Notice that the frameset specifies two frames of height 100% and * but in the frameset there's only one frame.
Assignee: asa → pollmann
Component: Browser-General → HTMLFrames
QA Contact: doronr → petersen
Summary: Mozilla goes into a loop → Mozilla goes into a loop with only one frame when two was specified.
Comment 6•24 years ago
|
||
Changing severity to critical since this causes the equivalence of a crash.
Severity: normal → critical
Assignee | ||
Comment 7•24 years ago
|
||
Adding crash keyword as this is a stability problem (requires restart)
Status: NEW → ASSIGNED
Keywords: crash
Reporter | ||
Comment 8•24 years ago
|
||
*Seems* to be fixed in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20000804
Assignee | ||
Comment 9•24 years ago
|
||
I am able to reproduce this still in today's build (FreeBSD)
Crash is bad, nominating for nsbeta3. I also advice upping priority to P1. This might be related to bug 42060, bug 40929 and bug 48382.
Keywords: nsbeta3
Assignee | ||
Comment 11•24 years ago
|
||
This is exactly the same scenario as bug 48382 - http://fastpris.cjb.net is a frameset document with a single frame. That frame contains this document: <html> <body onload="window.location='http://blueviper:8002/www.nasslan.net/kampanj/index.php'"> </body> </html> Marking this as a duplicate. Note that in recent builds, you can hit the X (stop) button and it will stop the infinite loop, so it's not quite as bad as it was before. Also note that the loop is pulling the page from the cache not hitting the server. *** This bug has been marked as a duplicate of 48382 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Core → Core Graveyard
Updated•6 years ago
|
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in
before you can comment on or make changes to this bug.
Description
•