Closed Bug 197350 Opened 22 years ago Closed 19 years ago

<frame src="#"> loads frameset -> infinite frames

Categories

(SeaMonkey :: General, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jsk_priv, Assigned: asa)

References

()

Details

User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030313 Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030313 Browsing to the page (see url), clicking on the 3. link (Wittenberge-Cuxhaven) below the picture opens a new page (http://www.elberadweg-r2.de/) that again opens countless instances of a popup window. Reproducible: Always Steps to Reproduce: 1. http://www.elberadweg.de 2. click third link (wittenberge-cuxhaven) 3. enjoy ;) Actual Results: large number of instances of a popup are displayed Expected Results: only one instance of the popup should be displayed Tested on: 1.4a (nightly) for OS/2 0.9.8 for linux
Confirming. I have to disable JS in order to avoid all those pop-ups. Using an one hour old CVS based trunk build - winXP-Sp1.
Status: UNCONFIRMED → NEW
Ever confirmed: true
WFM. 2003031308 / XP. I see a lot of "contacting" various URLs for a while, but Mozilla properly suppresses any pop-ups that might have occurred.
> 0.9.8 for linux Not useful. ;) You _do_ have popup blocking turned on in 1.4a, right?
The browser is installed with all defaults - so i guess the blocking is off ;) But still. One popup is enough imho.
Um... But isn't it the _page_'s problem then if it puts up too many popups? We just do what the page asks us unless the user overrides it via the popup blocking pref.
This is somehow tricky. Maybe this really is the webpage's problem. So this would come down to "to which extend should Mozilla provide corrections for webpage-programming-errors?". Still i think it is useful to suppress multiple identical popups. I cannot imagine a situation where it makes sense to show a popup several times - besides from jokes maybe ;) I still believe that suppressing double popups is a good thing, maybe there could be a dialog that informs the user that the page requests to open another one of the already existing popups. There should be an option to say "No, thanks, one is enough." On the other hand - this was the first page that ever showed such a problem. It simply might not be worth the effort ...
Let's start with "How is Mozilla supposed to know what's an error?". JavaScript is a tool. Like any tool it can be misused. Preventing misuse generally decreases utility. <shrug>.
Blocking misuse is a good thing. In this case this might even end up doing harm to the user's operating system when the resources are used up. I can even imagine this might a security risk of some sort...
How do you tell it's misuse? Is it misuse to document.write thousands of lines into the HTML document? That can also tie up resources....
setting severity to major problem: <frameset border="0" frameborder="0" rows="100%,*"> <frame ... src="http://www.altmarkweb.de/eleberadweg/index.htm" ...> <frame name="frame1" src="#" ...> <noframes>... </noframes> </frameset> the bottom non-visible frame is loading the frameset -> infinite frames
Severity: normal → major
Summary: Page opens unlimited number of popups → <frame src="#"> loads frameset -> infinite frames
Is it infinite or 50? We cap at 50 frames or something...
It looks like the page has changed. It does not pop up even one window, and the code indicated in comment #10 is not in the page.
http://tevp.net/test.html has now been set with some testing code for this problem. Looks fine to me on Firefox (Build: 20041030, Linux).
During some development, I noticed this bug exists also for iframes. Cut and paste the following code, you will see what I mean. I seems mozilla stops after 3 iterations. In my exampe, the page is somewhat simple, but if the page is larger, it will take a lot of time/cpu to display. ---------------------------------------- <html> <body> <h1> IFRAME recursive bug </h1> <iframe src="#"></iframe> </body> </html>
This bug is about _infinite_ frames. Stopping after 3 iterations is the right behavior; we're doing that quite purposefully.
Product: Browser → Seamonkey
so, invalid? (site may have been redesigned, I don't see the problem in IE)
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.