Create the following file as /tmp/file.xul, and start mozilla with: ./mozilla -chrome 'file://tmp/file.xul' An (presumably) endless loop occurs, with WEBSHELL+ = nn repeating with ever increasing values of nn. <?xml version="1.0"?> <!DOCTYPE window > <window id="main-window" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"> <html:iframe id="content-frame" src="file://tmp/file.xul" flex="100%"/> </window>

han.holl@prismant.nl what build were you testing this with? XPApps? XUL?

we'll see what jrgm has to say about this

Oops, sorry. Linux Build 2000032711, mozilla-i686-pc-linux-gnu.tag.gz ( 6178334 bytes) Platform: PentiomPro 200 and Pentium III 400. Han

Yes, this can be done. In the end, <html:iframe> simply depends on the implementation of <iframe> in the layout engine -- and that is bug #32389. I'll make this bug depend on that bug, so I can check that the XUL context is fixed when the base implementation is fixed (pretty much automatic). Peter -- you can just assign this to me if you want. [On a related note, I happened to be pondering this for overlays yesterday, and overlays can be called recursively (or in a cycle), leading to a crash. I'll file that bug now.]

you got it

Guessing that this is also a duplicate of bug 8065.

Yeah, this is really a duplicate of bug #8065, I just thought that I would keep this separate so that I remember to check that there are no odd, loose ends left for the <html:iframe> context when the <iframe> fix is finished. If there is no way in fish-hell that this could be different then just mark it DUPL.

This bug has not been touched for more than nine months. In most cases, that means it has "slipped through the net". Please could the owner take a moment to add a comment to the bug with current status, and/or close it. Thank you :-) Gerv

Nothing to be done but wait on bug 8065 (nee bug 32389).