This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15919 - Should test what happens if you do document.open() from within the unload algorithms (since it calls them back)
Summary: Should test what happens if you do document.open() from within the unload alg...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 22:29 UTC by contributor
Modified: 2012-09-21 22:08 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-02-06 22:29:59 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#opening-the-input-stream
Complete: http://www.whatwg.org/c#opening-the-input-stream

Comment:
Should test what happens if you do document.open() from within the unload
algorithms (since it calls them back)

Posted from: 2620:0:1000:147d:fa1e:dfff:fedd:ce8d by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.3 Safari/535.19
Comment 1 contributor 2012-07-18 16:07:10 UTC 
This bug was cloned to create bug 18044 as part of operation convergence.
Comment 2 Silvia Pfeiffer 2012-09-21 22:08:20 UTC 
Just to be complete, I this got fixed in 
http://html5.org/tools/web-apps-tracker?from=7303&to=7304