Well, POST data is actually delivered as-if a hidden query string. So, for a GET request, you have an HTTP QUERY_STRING and for a POST request you have a RAW_POST_DATA. Both are functionally equivalent and neither are scoped.
Look, it can and does work, and there's no reason to believe it will stop any time soon. But why use multiple <form> tags when one will do? Are they posting to different actions? Do they expect to know the contents of fields in the other form? Should the user expect to know the behavior of hitting enter when in one form or the other (can they really tell they are in a different form)? I'm not a fan, but if there's a clear argument why this is a simplifying practice, I'm all ears. On Dec 9, 2008, at 4:35 PM, Hassan Schroeder wrote: > Yes, you have to be careful with multiple forms on the page to not > have duplicate element IDs and whatnot, particularly if you're using > JavaScript. However, you can only /submit/ one form at a time, so > there should be no problem on the back end. > > And I'm not sure what that second sentence means, since POST data > isn't delivered as a "query string". > Can you clarify? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
