Opened 13 years ago
Closed 10 years ago
#3157 closed bug (fixed)
JSONP doesn't always correctly fire ajax events
| Reported by: | tandoan | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3 |
| Component: | ajax | Version: | 1.2.6 |
| Keywords: | jsonp events | Cc: | |
| Blocked by: | Blocking: |
Description
When making a remote call, jQuery.active is incremented, but never decremented properly, so ajaxStart and ajaxComplete events are not fired after the first ajaxStart.
Attachments (2)
Change History (5)
comment:1 Changed 13 years ago by
| need: | Review → Test Case |
|---|
Changed 13 years ago by
| Attachment: | smalltest.html added |
|---|
Changed 13 years ago by
| Attachment: | jsonreturn.html added |
|---|
comment:2 Changed 13 years ago by
Attached are 2 files, changing line 34 in smalltest.html so that jsonreturn.html is on a different server will cause the incorrect event behavior.
comment:3 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I think this has been fixed long ago...
Note: See
TracTickets for help on using
tickets.
I don't really see why. I checked the source and it doesn't depend on whether it is jsonp or not. Can you provide a test case to reproduce the error ? just a small html file that shows the problem.