This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html Section: http://www.whatwg.org/specs/web-apps/current-work/#input-type-attr-summary Comment: The text here says that an input element is always mutable and then says that “similarly” the user agent should not allow the user to modify the element's value or checkedness. The sense seems to be backwards. Not being allowed to modify something is immutability. Mutability is not similar to immutability. It’s opposite. Posted from: 76.103.57.93
It also seems that the specifications bug-reporting feature doesnt handle non-ASCII characters correctly.
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: The spec is correct, though I agree it looks contradictory at first glance. The paragraph in question is really just setting defaults, so that, e.g., you can't change the checkedness of a text field. I tried adding an informative note in the spec to clarify it but I couldn't come up with a good way of doing it that didn't end up taking far more prose than this is worth.
mass-move component to LC1