Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

404 Why 'catch' can't catch? #5

Closed
abel-oye opened this issue Jan 11, 2016 · 6 comments
Closed

404 Why 'catch' can't catch? #5

abel-oye opened this issue Jan 11, 2016 · 6 comments

Comments

@abel-oye
Copy link

404 Why 'catch' can't catch?

@camsong
Copy link
Owner

camsong commented Jan 11, 2016

You should be able to catch after a timeout(default to 5 seconds). JSONP uses a <script> to make request, when the <script> failed, the plugin is not informed, that's why I used setTimeout

@camsong camsong closed this as completed Jan 11, 2016
@abel-oye
Copy link
Author

@why use time out, Can not use script onload?

@camsong
Copy link
Owner

camsong commented Jan 28, 2016

Not sure if script onload supports IE8+?

@abel-oye
Copy link
Author

If supported, the onload is more appropriate?
And then use a timeout?

@camsong
Copy link
Owner

camsong commented Jan 29, 2016

yep, this would be great. Can you help to investigate this?

@camsong camsong reopened this Jan 29, 2016
@abel-oye
Copy link
Author

IE8 does not support the "onerror"; but you can determine whether to download through the onreadyState, and then through the characteristics of the callback, check the overall function jsonp, to verify the results.

@camsong camsong closed this as completed May 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants