On Nov 18, 8:27 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > Thanks Koz for a brief and Hongli for more detailed explanation, but I don't > think you got my question right. > > You guys are talking about (hidden) textual form controls that map to > booleans. That's fine. I'm talking about HTML attribute serialization in > general, meaning *everything besides* textual form controls mapping to > booleans, and why I think this commit should be reverted. This is the > reason: > > <% tag :input, :type => "checkbox", :checked => false %> > > Who here thought that this creates a text input that isn't checked? Well, > you thought wrong. This generates an initially checked box.
Good point. This has been fixed in http://github.com/rails/rails/commit/0f89ed5636f69c7ae75f99ca2a613b1918de5f95 I've registered 'checked' as a boolean HTML attribute so that it doesn't get outputted when its value is false. If you encounter more problems, then please suggest more attributes to register as boolean HTML attributes. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
