When these issues (with the original parser) were first raised because of prototype.js parser being different, and yet yielded the wanted results, I first opposed them. Lately I've seen how they could tighten up and improve complex forms. Having said that, I'm worried about backwards-compatibility. I don't think a single parser can support both schemes -- or am I wrong?
Still, should there be a switch one can toggle to start using the new parser after Rails 2.2? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
