Bug 14599 – document.write() inside an <iframe src> does not work

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: DOM

[Sridhar Gurivireddy]

Document.write() inside an iframe src should write to the <iframe>. Safari does not do anything.

e.g code
#######
 <frameset id="frameset" border="1" cols="50%,50%" style='border: solid 1px;'>
 <frame name="frame2" src="about:blank">
 <frame name="frame1" src="javascript:
       try { document.write('whatever'); } catch(e) { window.alert(e.description); }
 ">
 </frameset>

This works well in other browsers

[Alexey Proskuryakov]

Confirmed with r24241 on Mac OS X.

[Alexey Proskuryakov]

Created attachment 15496 [details]
test case

[David Kilzer (:ddkilzer)]

Not a regression as the reduction behaves the same way with Safari 2.0.4 (419.3) with original WebKit on Mac OS X 10.4.10 (2R218).  Tested with a local debug build of WebKit r24285 with Safari 3.0 (522.12) on 10.410.

[David Kilzer (:ddkilzer)]

(In reply to comment #2)
> Created an attachment (id=15496) [edit]
> test case

FWIW, this test case caused a crash in Firefox 2.0.0.4:

https://bugzilla.mozilla.org/show_bug.cgi?id=388181

[Justin Haygood]

Created attachment 15695 [details]
Testcase.. 2 files

2 file testcase in ZIP....

test.html opens up an iframe which uses document.write.

I believe the bug description is wrong, and the test case provide demonstrates a different bug? Can you really put framecontent inline with the mainpage? I've never seen that be done.

[Sridhar Gurivireddy]

I beleive basically the bug here is that document.write() does not update the content until document.close() is called.

javascript:document.write("sridhar") does not work in Safari, while
javascript:document.write("sridhar");document.close(); works

[Alexey Proskuryakov]

(In reply to comment #6)
> I beleive basically the bug here is that document.write() does not update the
> content until document.close() is called.

This sounds like a duplicate of bug 8961.

[Adam Barth]

Yep.  My patch for Bug 8961 fixes this one too.

*** This bug has been marked as a duplicate of bug 8961 ***