Side navigation
#8427 closed bug (wontfix)
Opened March 02, 2011 10:03PM UTC
Closed March 03, 2011 12:09AM UTC
Last modified March 14, 2011 06:22PM UTC
similar bug as Ticket #8107
| Reported by: | kontakt@kiwisaft.de | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.next |
| Component: | ajax | Version: | 1.5.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Attachments (0)
Change History (2)
Changed March 03, 2011 12:09AM UTC by comment:1
| component: | unfiled → ajax |
|---|---|
| resolution: | → wontfix |
| status: | new → closed |
Changed March 14, 2011 06:22PM UTC by comment:2
Replying to [comment:1 jaubourg]:
Why on earth would you use call ajaxSetup with no parameter? What purpose would it serve? http://api.jquery.com/jQuery.ajaxSetup/ As you can clearly see in the doc, the options are NOT optional. That's a totally different case from #8107 where a documented signature didn't work. The workaround you provide is not a workaround at all, it's actually the correct way to call ajaxSetup so that it does... nothing.
The doc says:
jQuery.ajaxSetup( options )
options A set of key/value pairs that configure the default Ajax request. All options are optional."
So I guess, I don't need ajaxSetup() if I don't serve any options to it, right?
Why on earth would you use call ajaxSetup with no parameter? What purpose would it serve?
http://api.jquery.com/jQuery.ajaxSetup/
As you can clearly see in the doc, the options are NOT optional. That's a totally different case from #8107 where a documented signature didn't work. The workaround you provide is not a workaround at all, it's actually the correct way to call ajaxSetup so that it does... nothing.