Since we are discussing the IPE's defaults, there's something that bugs me, but since I haven't looked much into it, I could have missed something: The ajaxOptions are shared between loadText requests and when saving the serialized form.
Now, if I want to save the form with a PUT request (using rails restfulness bliss :)), since the default when saving is using POST, I have to pass it in the ajaxOptions. But that will overwrite the GET method of the loadText request :-\ Am I missing something? I will need the IPE soon, so I guess I'll either find out if I read it all wrong or I'll come up with a patch :) -Nicolas On Nov 16, 2007 3:55 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > The default behavior of the request in the InPlaceEditor seems to be > that it sends the entire serialized params object, which is an > extended object, as the parameters of the request. So all of the > methods like all(), any(), and so on are serialized and sent as > parameters. When I view the headers of the request I can see all of > them. > > Is that the intended behavior? It seems wrong, since my server-side > code obviously has no use for JavaScript methods. If my server-side > code happens to be looking for a parameter named include or size, it's > not going to be happy. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
