Ticket #8427 (closed bug: wontfix)
similar bug as Ticket #8107
| Reported by: | kontakt@… | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.next |
| Component: | ajax | Version: | 1.5.1 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
Change History
comment:1 follow-up: ↓ 2 Changed 2 years ago by jaubourg
- Status changed from new to closed
- Resolution set to wontfix
- Component changed from unfiled to ajax
comment:2 in reply to: ↑ 1 Changed 2 years ago by kontakt@…
Replying to 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?
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.
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.