Bug 145687 – Ignore radio buttons with different associated forms on keydown when the form element is descendants of main form.

• Component: DOM
• Status: NEW

[Rohit]

Currently if a new form is encountered on key down in a radio group, the pressing keydown does not jump to another next radio button in the group. We should just ignore radio buttons with different associated forms. The associated form element of a control may have a form element as one of its descendants. It can happen in case of mixing buttons from different form control groups and other elements.

Webkit should handleccomplicated cases Like, mixing buttons from different groups and other elements.

<input type=radio name=foo>
<input type=radio name=bar>
<div><input type=radio name=foo></div>

And attaching form elements to form elements
<form name=alpha>
<input type=radio name=foo>
<input type=radio name=foo>
</form>
<form name=beta>
<input type=radio name=foo>
</form>
<script>
document.alpha.appendChild(document.beta);
</script>

[Rohit]

Created attachment 254347 [details]
Patch

[Darin Adler]

Comment on attachment 254347 [details]
Patch

Change seems OK. One small problem is that we’ll now always traverse the entire document once we are past the last radio button. That could take a long time.

[Rohit]

Thanks Darin. 

I am working on a patch that will cycle the radio button in a group on "downArrow"/"upArrow" keydown event when we reach the last/first radio button in a group. That should solve the entire document traversal issue. I will raise the bug and submit it soon.

[Lucas Forschler]

Mass move bugs into the DOM component.

[Ryosuke Niwa]

Comment on attachment 254347 [details]
Patch

This 3.5 year old patch is probably not going to land properly.