Skip to main content

Bug Tracker

Side navigation

#14499 closed bug (invalid)

Opened October 31, 2013 06:35AM UTC

Closed November 25, 2013 08:31AM UTC

ajaxComplete incomplete documentation

Reported by: Marc-André Lafortune <> Owned by: Marc-André Lafortune <>
Priority: undecided Milestone: None
Component: unfiled Version: 1.10.2
Keywords: Cc:
Blocked by: Blocking:

The documentation for ajaxComplete explains the argument will be called whenever an ajax request completes. At the end, there's a single caveat that states "If $.ajax() or $.ajaxSetup() is called with the global option set to false, the .ajaxComplete() method will not fire".

This caveat is incomplete. Indeed, if $.ajaxSetup is never called and $.ajax is called without a 'global' option but with a cross-browser request, then $.ajax will set the global option and the ajaxComplete argument will not be called.

Same can probably be said for the other global ajax events.

Please complete the doc and save others for wasting quite a bit of time figuring this out.


Attachments (0)
Change History (2)

Changed November 10, 2013 07:12PM UTC by dmethvin comment:1

owner: → Marc-André Lafortune <>
status: newpending

Can you recommend the specific wording change you'd like to see? You can file a pull request against the docs at .

Changed November 25, 2013 08:31AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!