Bug 65407 – Webkit doesn't clear timeouts and intervals when open() is called on a document that's not already open

• Component: DOM
• Status: NEW

[Tobias Markus]

Created attachment 102424 [details]
testcase

As per https://bugzilla.mozilla.org/show_bug.cgi?id=675399#c1 and http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#dom-document-write, calling of document.write after parsing is done should trigger a new document object to be created (please refer to that bug for proper explanation:
---
You're calling document.write() after parsing is done.  Per http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#dom-document-write step 3, this triggers a call to open().

Then http://www.whatwg.org/specs/web-apps/current-work/multipage/content-models.html#dom-document-open step 12 replaces the window associated with the document with a new window.  The list of timeouts is attached to the old window, so goes away.

WebKit just gets this wrong.  Please report the problem to them....
---

[Alexey Proskuryakov]

Created attachment 102580 [details]
updated test case

That text means that the first call to document.write() after parsing is done should replace original content, and that's what happens in both WebKit And Gecko. But why does the insertion point become undefined after the first document.write()?

[Boris Zbarsky]

The issue is not the insertion point.  The issue is that the open() should clear the interval (because it sets up a new Window), but doesn't seem to in WebKit.

[Alexey Proskuryakov]

Thanks, that makes sense. We don't set up a new document or window on document.open() though, we just remove all children of the existing document, and do some other cleanup. But custom properties all survive, too.

This doesn't feel like a typical WebKit bug, perhaps we're matching IE or older Gecko.

[Adam Barth]

I don't know the history of why we have the current behavior, but we should probably match other browsers.