17832 2012-07-18 06:58:19 +0000 'radio button group' rule issue 2012-09-26 22:33:45 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED P3 normal Unsorted 1 contributor ian adamk ian mike tkent contributor oldest_to_newest 70134 0 contributor 2012-07-18 06:58:19 +0000 This was was cloned from bug 16400 as part of operation convergence. Originally filed: 2012-03-16 07:30:00 +0000 Original reporter: Kent Tamura <tkent@chromium.org> ================================================================================ #0 Kent Tamura 2012-03-16 07:30:34 +0000 -------------------------------------------------------------------------------- http://dev.w3.org/html5/spec/Overview.html#radio-button-group If we follow the rules of 'radio button group', an orphan radio button and non-orphan radio button are in a same group. It makes some problems. For example, <body> <input type=radio name=group1 id=r1 checked> <script> var clone = document.getElementById('r1').cloneNode(); </script> </body> The r1 button is unchecked because the 'clone' is added to the same group. Proposal: Update the following sentence: * Either a and b have the same form owner, or they both have no form owner. ==> * Either a and b have the same form owner, or they both are in a Document subtree and have no form owner. ================================================================================ #1 Simon Pieters 2012-03-16 13:27:24 +0000 -------------------------------------------------------------------------------- or maybe: * Either a and b have the same form owner, or they both are in the same Document subtree and have no form owner. ================================================================================ 74595 1 contributor 2012-09-26 22:33:45 +0000 Checked in as WHATWG revision r7412. Check-in comment: radio buttons in different DOM trees can't possibly be related to each other http://html5.org/tools/web-apps-tracker?from=7411&to=7412