Opened 10 years ago
Closed 10 years ago
#7189 closed bug (wontfix)
xhr.abort() triggers error
| Reported by: | matas | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.4.3 |
| Component: | ajax | Version: | 1.4.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
the ajax error gets triggered when aborting the xhr. the 1.4.2 would ignore it.
if the behavior is expected, then how should we distinguish the aborted xhr's from 'regular' errors?
Change History (1)
comment:1 Changed 10 years ago by
| Component: | unfiled → ajax |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
This is expected - before it would trigger a success which was not desired. You could just keep track of when you call .abort() and handle that explicitly - overwhelmingly, though, calling a .abort() will trigger the same error conditions as a true error (cleaning up loading indicators, etc.)