Side navigation
#7189 closed bug (wontfix)
Opened October 14, 2010 04:18PM UTC
Closed October 14, 2010 04:45PM UTC
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?
Attachments (0)
Change History (1)
Changed October 14, 2010 04:45PM UTC by comment:1
| component: | unfiled → ajax |
|---|---|
| resolution: | → wontfix |
| status: | new → closed |
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.)