-
Notifications
You must be signed in to change notification settings - Fork 28
Open
1 / 21 of 2 issues completedLabels
Description
I thought the “error” event would be thrown for network errors (status 0), but it is only thrown for server errors.
So, if I want to handle all XMLHttpRequest errors at one place, I can go back to using a single “readystatechange” listener with this.readyState === XMLHttpRequest.DONE (4):
https://github.com/search?q=repo%3Ajesus2099%2Fkonami-command+XMLHttpRequest&type=code
- jasrac-mb-minc_WORK-IMPORT-CROSS-LINKING
- kasi_PLAIN-TEXT-LYRICS
- mb. MERGE HELPOR 2
- mb_ALL-LINKS
- mb_COLLECTION-HIGHLIGHTER Collection highlighter gets stuck after network error #944
- mb_FUNKEY-ILLUSTRATED-RECORDS
- mb_HYPER-MOULINETTE
- mb_INLINE-STUFF
- mb_MASS-MERGE-RECORDINGS
- mb_PENDING-EDITS
- mb_POWER-VOTE
- mb_PRINT-ALL-PAGES
- mb_SUPER-MIND-CONTROL-II-X-TURBO RELEASE_CLONER xhr_release_cloner error #945
- ymail-basic_DIRECT-LINKS-TO-MUSICBRAINZ
Reactions are currently unavailable