Thanks for your response Michael. I guess I should have clarified that I'm using Rails built-in helpers like form_remote_tag and link_to_remote, which generate the JavaScript for us. Extending either JS or Rails seems like an adequate fix, for now.
-justin On 4/18/07, Michael Peters <[EMAIL PROTECTED]> wrote: > > mr_justin wrote: > > Nobody has run into this? It is impossible to submit empty form fields > > through Ajax with this new behavior in Prototype. > > Sorry no-one has responded yet. It's been talked about quite a bit. > > http://groups.google.com/group/prototype-core/browse_thread/thread/711012b806b3ad36/75b3de9077ec6007#75b3de9077ec6007 > http://groups.google.com/group/prototype-core/browse_thread/thread/83996a20fecd61c4/8775c0b24361ae60#8775c0b24361ae60 > > It has been fixed in SVN and is scheduled to be in 1.5.1 > > > The best solution is > > to just switch forms to use normal POSTs, that's lame. > > You might try passing parameters as an object instead of a string so that > toQueryParams() is not called. > > new Ajax.Request('/', { parameters: { x: '', y: '', foo: 'bar' } } ) > > -- > Michael Peters > Developer > Plus Three, LP > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
