Re: Is null document.location expected in this case or a bug?
smaug <[email protected]> Mon, 24 Oct 2011 23:05:56 +0300
| Newsgroups | gmane.comp.mozilla.devel.dom |
|---|---|
| Message-ID | <[email protected]> |
On 10/24/2011 08:49 AM, [email protected] wrote: > event.target is still the old document. If the old document is (partially > or completely) gone, does it make sense to fire a DOMContentLoaded, whose > meaning is that the dom of the target (current document) is ready? Well, at the time your listener handles DOMContentLoaded, some other DOMContentLoaded listener may have caused the window.document to change. -Olli