Certainly a bug. But I wonder how many others have accidently allowed this to occur?
Deco On Oct 24, 2006, at 3:35 PM, Michael Peters wrote: > > > > Colin Mollenhour wrote: >> Whoa! Why is this a bug? > > Because Form.Serialize is supposed to give you back what the > browser would > submit as the forms data. It's the same reason that when prototype > serializes a > select box and uses the <option>'s text as the value instead of the > value when > the value is the empty string is a bug (#5033). It's not what > browsers are > supposed to do. > > Btw, Thomas, any reason why #5033 isn't fixed as well? > > -- > 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 -~----------~----~----~----~------~----~------~--~---
