Re: Is null document.location expected in this case or a bug?

On 10/23/11 5:56 PM, [email protected] wrote:
> In appcontent.DOMContentLoaded for an iframe, which in an inline script
> changes parent.location and then assigns its own location to about:blank,
> document.location is null, window.location is about:blank and document.URL
> is the actual url.
>
> Even though location has been changed before DOMContentLoaded, the
> navigation presumably has not started

If document.location is null, then not only has navigation started but 
the new document is already partway through being loaded and the old 
document is not the current document in the window, I would think...

You can tell this also from the fact that window.location is about:blank.

> Why are document.location and window.location out of sync?

Are document and window.document equal?

-Boris