Are you asking about the <input type=color> feature generally, or autocomplete on <input type=color>?

If the latter, color inputs have a value.  The browser may remember this value, and so controlling the autocomplete behavior for it seems roughly as useful as doing so for any other input.

mass-moved component to LC1

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: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 1

I would expect <input type=color> to render as a color picker, and I can't see what autocomplete would mean for a picker.  What does autocomplete on a color picker do?

(In reply to comment #4)
> I would expect <input type=color> to render as a color picker, and I can't see
> what autocomplete would mean for a picker.  What does autocomplete on a color
> picker do?

The picked color is a value.  If the browser remembers that value, then autocomplete can ensure that the input starts with that color chosen.

Thanks, that makes sense.  Can we add that sentence to the spec?

We can definitely add a non-normative note to the spec that clarifies that browsers can remember user input. Can you clarify why this is unclear for type=color but not for the other form controls? (It would help me with working out how to make this clearer.)

Cynthia, please see comment #7:
> We can definitely add a non-normative note to the spec that clarifies that
> browsers can remember user input. Can you clarify why this is unclear for
> type=color but not for the other form controls? (It would help me with working
> out how to make this clearer.)

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: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 7

I'm having a hard time understanding how the UI would work for this in a color picker.  If type=color is rendered as a text field, it would have a dropdown for autocomplete, like any other text field.  But if it is rendered as a color picker, what would the autocomplete look like?  Maybe just say that the autocomplete is only used if type=color is rendered as a text box?

(In reply to comment #10)
> I'm having a hard time understanding how the UI would work for this in a color
> picker.  If type=color is rendered as a text field, it would have a dropdown
> for autocomplete, like any other text field.  But if it is rendered as a color
> picker, what would the autocomplete look like?

If I picked red last time, it could automatically show red selected rather than requiring me to manually select it again.

--
Benjamin Hawkes-Lewis