This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Input elements suffers from value missing when: "the element is required, and its value IDL attribute applies and is in the mode value, and the element is mutable, and the element's value is the empty string". This is not including, 'file', 'radio' and 'checkbox' types because they are not in the value mode. An input element in those states have specifics rules but it looks like these specific rules forgot to mention "and the element is mutable" that means, at the moment, an immutable checkbox/radio/file could be suffering from value missing even if you can't change the value... I think 'file', 'radio' and 'checkbox' specific rules should mention the element has to be mutable to suffer from value missing.
For radio buttons, the rules should also mention the _mutable_ radio button in the group have to be checked, like: "If the element is required and the element is mutable all of the mutable input elements in the radio button group have a checkedness that is false, then the element is suffering from being missing."
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: For file, checkbox, and radio to be immutable, they have to be disabled (readonly doesn't affect them). If they are disabled, they're not candidates for constrain validation at all, so it doesn't matter what their state is.
I know a disabled element is not a candidate for constraint validation but I think it would be better to remember an immutable element can't suffer from being missing even if in the present situation, it can't be immutable _and_ candidate for constraint validation. In my opinion it is not safe to consider that it's not possible at the moment so it doesn't worth to add it. But that's probably a dev point of view and I'm not re-opening this bug because of that... Actually, I'm wondering how to manage this situation: when a radio button is required and another radio button is checked in the radio group but this radio button is disabled. According to the current specification, the radio buttion shouldn't suffer from value missing. Is that the behavior wanted ?
By the way, sorry to insist but: "When an input element does not have a Document node as one of its ancestors (i.e. when it is not in the document), it is immutable." So, at the moment, radio/checkbox/file can suffer from value missing when they are immutable. Recently the specs have changed so an element is candidate for constraint validation even if it has no form owner.
(In reply to comment #3) > I know a disabled element is not a candidate for constraint validation but I > think it would be better to remember an immutable element can't suffer from > being missing even if in the present situation, it can't be immutable _and_ > candidate for constraint validation. In my opinion it is not safe to consider > that it's not possible at the moment so it doesn't worth to add it. I'm not really sure I follow. There doesn't seem to be any point worrying about what the state of a control when it's disabled. What problem would it solve? > Actually, I'm wondering how to manage this situation: when a radio button is > required and another radio button is checked in the radio group but this radio > button is disabled. According to the current specification, the radio buttion > shouldn't suffer from value missing. Is that the behavior wanted ? Yes. > "When an input element does not have a Document node as one of its ancestors > (i.e. when it is not in the document), it is immutable." > So, at the moment, radio/checkbox/file can suffer from value missing when they > are immutable. True, though if they're out of the document, it doesn't much matter. 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: Being out of the document isn't especially important either.