This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#htmlformcontrolscollection-0 Comment: Get rid of RadioNodeList Posted from: 91.181.36.60 by ms2ger@gmail.com
Or at least explain why the use case presented in <http://lists.whatwg.org/pipermail/commit-watchers-whatwg.org/2009/002152.html> is anywhere near the right side of the 80/20 divide.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: It turns out that people dynamically changing the value of form controls happens a _lot_, including radio buttons. One of the biggest pain points of doing so is setting the value of radio buttons. One of the others is setting the value of <select>, which I deferred for now.
If you say so.