Expected behavior with XmlHttpRequest.abort() and ajaxStop event

Expected behavior with XmlHttpRequest.abort() and ajaxStop event


Hi,
I have a question related to a bug in Tabs:
http://ui.jquery.com/bugs/ticket/3903
So I'm using the XmlHttpRequest abort method to cancel a running
request if another tab is being selected. In that case no ajaxStop
event is fired for the former (obsolete) request.
I am now wondering what the expected behavior is here. Would it be
expected to fire ajaxStop for such a canceled XHR request? In that
case it wouldn't be a bug in tabs but in jQuery itself. If the current
behavior is as expected, the bug would probably be invalid.
Thanks,
--Klaus