On Thu, May 7, 2009 at 2:22 PM, zambezi <b.but...@overhydration.org> wrote:
> It appears that some ivory towered radio button designer never > conceived that a user might click on a radio button group, change > their mind and want to undo the click therefore returning to a false- > false state. Quoting the HTML 4 spec: If no radio button in a set sharing the same control name is initially "on", user agent behavior for choosing which control is initially "on" is undefined. Note. Since existing implementations handle this case differently, the current specification differs from RFC 1866 ([RFC1866] section 8.1.2.4), which states: At all times, exactly one of the radio buttons in a set is checked. If none of the <INPUT> elements of a set of radio buttons specifies `CHECKED', then the user agent must check the first radio button of the set initially. Since user agent behavior differs, authors should ensure that in each set of radio buttons that one is initially "on". </quote> If you want a "no preference" option, you should provide one explicitly. FWIW, -- Hassan Schroeder ------------------------ hassan.schroe...@gmail.com --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
