Garrett Smith wrote:
Are you asking: What if the loadend handler calls open() on the same
connection in loadend?
Right.
When loadend is called, the actual completion event ("abort" | "fail"
| "load" ) has not fired.
Calling open should cause the previous connection to end. Jonas
suggested that the corresponding event ("abort" | "fail" | "load")
should then fire unless e.preventDefault() is called.
That is ok to me, even without the default behavior.
This is just something to mention in the XHR2 spec.
And the spec should handle also cases like calling abort() in loadend
handler etc.
Just curious: Why call open() again in loadend?
I don't know. But I'm sure someone will write such script.
-Olli
