W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2010

[Bug 9505] Immutable checkbox, radio and file input types should not suffer from value missing

From: <bugzilla@jessica.w3.org>
Date: Thu, 15 Apr 2010 06:59:51 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1O2J3H-00009z-1o@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #5 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-04-15 07:03:49 ---
(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 ?


> "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:

Status: Rejected
Change Description: no spec change
Rationale: Being out of the document isn't especially important either.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 15 April 2010 07:03:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:16 UTC