-
Notifications
You must be signed in to change notification settings - Fork 20.6k
jQuery.param
’s behaviour differs with the one described in the docs
#3023
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
Comments
Nice catch, @sowcow! Would you like to submit a PR? |
Yes, I'm looking forward to it. |
Probably I should also modify ajax.js, i will check that tomorrow. |
I think i'm done, comment if any fixes are needed. |
Everyone agrees this is ready to land? If so I'll land it for master/3.0, update the 3.0 upgrade guide, and submit a docs ticket to change the version to 3.0. Ugh, I guess we'll also need a Migrate ticket. |
One thing I just realized, the tests here were covering the case for @sowcow would you be able to do that? You can use this test as a template because it does something very similar. Just pass in |
I'll do that tomorrow. |
For reference, PR is in #3030. |
sorry @sowcow should have pinged you here since the action item was here. |
sorry, I'm a bit irrational about tests, so i can't do that ⛄ |
Fixes jquerygh-3023 Since .param() no longer looks at this setting we need unit tests to ensure it is still honored by $.ajax().
docs
http://api.jquery.com/jQuery.param/
As of jQuery 1.8, the
$.param()
method no longer usesjQuery.ajaxSettings.traditional
as its default setting and will default tofalse
. For best compatibility across versions, call$.param()
with an explicit value for the second argument and do not use defaults.actual
https://github.com/jquery/jquery/blob/master/src/serialize.js#L65
The text was updated successfully, but these errors were encountered: