[Bug 10581] Drop the color input type

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10581





--- Comment #6 from Shelley Powers <shelleyp@burningbird.net>  2010-09-08 21:51:38 ---
(In reply to comment #5)
> (In reply to comment #4)
> > Actually, I believe the Webkit implementation is still in effect? Unless
> > there's another bug where it was removed.
> 
> It may still be around in the public builds, but I'm fairly certain it's gone
> in higher channels, which means it'll disappear as autoupdate proceeds.
> 
> > 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.
> 
> Color pickers, like date pickers, offer the potential of quite a lot of UI
> customization.  In practice, date pickers don't need that level of UI
> customization to be perfectly usable for the vast majority of authors.  I
> believe color pickers are the same.  As long as the color picking doesn't suck,
> I'll be more than happy to just use it.
> 
> As with date pickers, authors who really do want advanced control over the
> widget's display can continue to use javascript-based implementations like they
> do today.  I strongly believe that the fraction who will go to the effort of
> doing so when they could instead just write <input type=color> in their pages
> will be minuscule.

No, I don't think so. I don't think people are going to be interested in
yanking what they have now, just to incorporate something that is inferior.
Remember, we've had this as a packaged JS UI control for some time now. 

Most color picking will be a drop down list of a given set of colors. It's only
with the rare graphics app, such as the color picker incorporated into Drupal
that needs anything more. And it already has something incorporated. 

When you have applications that already use JS, such as the drawing program you
mention, they don't get anything by trying to incorporate a declarative color
picker. Especially if the people are also working with canvas or SVG.

We'll have to disagree on this.

-- 
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 21:51:40 UTC