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

[Bug 10581] Drop the color input type

From: <bugzilla@jessica.w3.org>
Date: Wed, 08 Sep 2010 20:52:56 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OtRdY-0004Yw-SY@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10581





--- Comment #4 from Shelley Powers <shelleyp@burningbird.net>  2010-09-08 20:52:56 ---
(In reply to comment #3)
> Your statement is technically correct, but still shows that you're
> misunderstanding the basic issue.  The formatting of the @value has no
> relevance to the user, any more than the precise data structure exposed by a
> file input does.  The input exposes a widget that allows the user to choose the
> color, and then serializes that color in some fashion for storage in the DOM.
> 
> A browser is free to expose any input method they would like for color inputs. 
> The color palette is recommended, but if they wish to offer more "advanced"
> inputs, such as letting the user input a color directly in rgb or hsl or by
> name, that's perfectly fine too.  All of these are directly convertible into a
> 6-hexit RGB value without significant dataloss.  The limitations on the field
> that you reference in your original comment do not exist.
> 
> I don't understand what you mean by "most drawing programs allow you to specify
> color formatting".  My drawing programs expose multiple methods of *entering* a
> color, yes.  They don't expose anything about color *formatting*, though, as
> serializing a color is an irrelevant concern.
> 
> Maybe you were misled by the temporary incomplete implementation of some of the
> input types in Webkit browsers?  They did temporarily turn on constraint
> validation for some input types without also supplying the appropriate input
> widgets, which caused some confusion similar to what you're expressing about
> the "usability" of only allowing the user to enter hex colors.  The input was
> never intended to act like a restricted text input.

Actually, I believe the Webkit implementation is still in effect? Unless
there's another bug where it was removed.

Regardless, following is a description of using one color picker, the YUI 2
Color Picker Control:

http://developer.yahoo.com/yui/colorpicker/#using

Notice how much control a web developer or designer has? And this is just one
from the many we can choose from.

Most color pickers provide a great number of UI customizations. Whether to show
the hex value, whether to just show colors, how to display the colors, whether
to show the RGB values--whether to enable input of a hex or RGB value directly.
Alpha transparency support. 

This color picker gives us none of this. None. Zero, zip. You get what the
browser companies give you, and that's it. 

So no, it fares poorly, abysmally, compared to what we have had in the last six
years since the color picker input type was first proposed.

-- 
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 Wednesday, 8 September 2010 20:52:58 UTC

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