Open Bug 473396 Opened 16 years ago Updated 2 years ago

Firefox does not draw appended contents of DOM created empty iframe.

Categories

(Core :: DOM: Core & HTML, defect)

defect

Tracking

()

People

(Reporter: bugs, Unassigned)

References

(Depends on 1 open bug, )

Details

Attachments

(2 files)

The testcase page details the issue, I will also add it as an attachment.
The page derived out of testing how browsers handle nested frames.  I hit the expected 10 frame limit in Firefox, however I noticed it was not actually drawing any content I put in the frame (as well as iframe and text node, tried various tags like h1 too).  It wouldn't throw an exception, they'd append fine, they just wouldn't show up.
Attached file Demo of problem.
In a debug build, I get:

WARNING: Too many nested content frames have the same url (recursion?) so giving up: file /Users/bzbarsky/mozilla/css-frameconst/mozilla/content/base/src/nsFrameLoader.cpp, line 999
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x8000FFFF: file /Users/bzbarsky/mozilla/css-frameconst/mozilla/content/base/src/nsFrameLoader.cpp, line 182

Perhaps we should skip doing that check for cases when the src is about:blank or empty or whatnot?
Component: General → DOM
Product: Firefox → Core
QA Contact: general → general
Another option is to not return an error nsresult for a recursive load; just return NS_OK and don't do the load.
Either of those solutions sound fine to me
Flags: needinfo?(bzbarsky)
I'm going to post a WIP that doesn't quite fix this, because we never end up with a usable document in the subframe.  Fixing that probably requires fixing bug 543435 first.
Depends on: sync-about-blank
Flags: needinfo?(bzbarsky)
Attached patch WIPSplinter Review
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: