Blocking Chromium, see bug http://code.google.com/p/chromium/issues/detail?id=3138 Seems like a strange thing to do but it turns out that in IE and FF you can select a radio button without a name.
You sure about IE? Not letting you select a radio button without a name was deliberately copying IE. Maybe they changed it in IE7 or 8.
What does it mean to be "Blocking Chromium"?
I checked IE 7 and it does allow you to select the radio buttons at the top of the example page which do not have names so they must have changed IE. When I said Blocking Chromium I just meant that this is a copy from the Chromium bug database. Perhaps I should pick different words to reflect different priorities?
Created attachment 25546 [details] in-process patch for issue 21534 IE7 and IE8 Beta (and Firefox) allow the user to check the radio button even if the name is not set. Here's an in-progress patch that simply removes logic that returns when the radio button name is not set. I need to run more layout tests to see if this has any other adverse effects.
Created attachment 25804 [details] Possible patch for issue 21534 IE6 (and an earlier version of 7) had a quirk where they would not allow unnamed radio buttons to be selected. WebKit mimicked this behavior. However, now IE7 and 8 do allow the user to select unnamed radio buttons. This patch modifies HTMLInputElement's behavior to treat named and unnamed radio buttons the same. That is, this patch removes the checks that explicitly look for unnamed radios. The only check that remains is in HTMLFormElement, which checks for radio button naming for grouping. Unnamed radio buttons should not be grouped and can be selected ("on") simultaneously. IE and FF behave this way, so I didn't modify this behavior. This patch brings WebKit's behavior to parity with FF/IE7&8.
Comment on attachment 25804 [details] Possible patch for issue 21534 r=me
*** Bug 16337 has been marked as a duplicate of this bug. ***
Committed revision 39791.