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

[Bug 9357] input element color state should be able to suffer from a type mismatch

From: <bugzilla@wiggum.w3.org>
Date: Fri, 02 Apr 2010 06:56:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Nxanl-0003J4-V7@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9357


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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-04-02 06:56:19 ---
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's impossible for a color picker to be in a type mismatch state
because the user agent is required to prevent the user from ever entering such
a state. If WebKit's implementation can be in such a state then it is buggy.


-- 
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 Friday, 2 April 2010 06:56:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 2 April 2010 06:56:23 GMT