I like that idea. I don't see any downsides for that. Are there performance differences when submitting an multipart form?
On Jun 14, 9:33 pm, joost <[email protected]> wrote: > Forms without explicit enctype are submitted as application/x-www-form- > urlencoded. This is the default behaviour in Rails. However, this > enctype does not allow transmission of binary data (files). > > Would it not make sense to specify the enctype multipart/form-data by > default instead? i.e. all the form_for helpers would add this enctype > to the form tag, unless overriden by the developer. > > This way, file uploads "just work" and normal key/value pairs continue > to work as well. There is no downside. I browsed through lighthouse > and only found obscure NN4 bugs related to multipart/form-data, which > I believe we can safely ignore. Even IE4 supports this enctype. > > I can fork and make this change, but would like to float this idea > beforehand. -- 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.
