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
Remove deprecated ajax methods #2084
Comments
Would be fine with me. If we are making a lot of changes for Promise/A+ compliance that would also move people towards the standard methods. |
Sounds good to me! Let's also open a ticket on jQuery migrate tho. |
Just created docs issue about it too |
Per the blog post that links here, this change means that |
@jfbrennan this ticket doesn't say anything about |
@dmethvin "Per the blog post that links here" it makes it sound like (1,443 upvotes and it says "As of jQuery 3, the ajax method returns a promise without extra methods (like abort)") https://stackoverflow.com/questions/446594/abort-ajax-requests-using-jquery/446626#446626 https://stackoverflow.com/questions/40421186/how-to-abort-a-jquery-3-0-ajax-request |
Can you point (as in a URL) to any official jQuery documentation that says |
http://blog.jquery.com/2016/01/14/jquery-3-0-beta-released/ says: "Removed special-case Deferred methods in jQuery.ajax jqXHR object is a Promise, but also has extra methods like .abort() so that you can stop a request after it has been made. As users increasingly embrace the Promise pattern for asynchronous work like AJAX, the idea of having special cases for the Promise returned by jQuery.ajax is an increasingly bad idea." Kind of implies that |
@dmethvin I am updating the SO answer to reflect reality, but can someone clarify what this statement means in the context of
Is this statement saying that although not removed at this time, |
@winzig thanks for the help! Yes |
jqXHR.success | error | complete
. They was deprecated since 1.8.Is it time to remove them?
The text was updated successfully, but these errors were encountered: