Good question - is this still the case in 1.3.1? If so, I think this would make for an appropriate bug to file.
--John On Sat, Jan 24, 2009 at 10:19 AM, Klaus Hartl <klaus.ha...@googlemail.com> wrote: > > 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 > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
