On 12/14/12 11:54 AM, Anne van Kesteren wrote:
On Fri, Dec 14, 2012 at 5:30 PM, Boris Zbarsky <[email protected]> wrote:
But note that you can get the same effect by just navigating the a browsing
context, then calling a function that was defined in the no-longer-active
document, without worrying about browsers that have buggy open()
implementations.
The specification deals with that by having xhr.open() throw.
Ah, indeed. OK.
I suppose the same would happen for the other case, since the associated
Document object is no longer active.
Which other case? The document.open() one? In that case, there is no
problem with the document per se; the only question is whether the XHR
has an associated document object at all in that case... and per spec
not having one does NOT cause open() to throw.
-Boris
