Intent to Prototype: InputTypeColorEnhancements

11 views
Skip to first unread message

Chromestatus

unread,
2:16 PM (6 hours ago) 2:16 PM
to blin...@chromium.org, cg...@chromium.org
Contact emails
cg...@chromium.org

Specification
https://html.spec.whatwg.org/multipage/input.html#attr-input-colorspace,https://html.spec.whatwg.org/multipage/input.html#dom-input-alpha

Summary
Adds support for the alpha and colorspace attributes on <input type=color>, matching the WHATWG HTML specification. When enabled, the color input gains an alpha boolean attribute (allowing non-opaque colors) and a colorspace attribute (limited-srgb or display-p3), and its CSS color parsing and serialization are expanded to support any CSS color value rather than only opaque hex colors. Both attributes are gated behind a single runtime flag.

Blink component
Blink>DOM

Web Feature ID
input-color

Motivation
Historically <input type=color> only supported opaque sRGB colors expressed as 7-character hex values, with no way to express transparency or wide-gamut colors. Developers building design tools, drawing applications, and theming interfaces have had to build custom color pickers to offer an alpha channel or access to wider color gamuts such as Display P3, increasing complexity and inconsistency across the web. The HTML specification now defines two attributes to address this: alpha, which lets users pick non-opaque colors, and colorspace, which selects the color space (limited-srgb or display-p3) and hints at the desired picker UI. Supporting these attributes lets the native control handle alpha and wide-gamut color selection directly, expands the control's value parsing and serialization to accept any CSS color, and brings Chromium in line with the standard. WebKit has shipped support for these attributes, enabling them by default via https://github.com/WebKit/WebKit/pull/35427. Firefox has partially implemented them (currently in Nightly behind a flag, desktop only), tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=2047120. Implementing them in Chromium improves interoperability for developers.

Initial public proposal
No information provided

Goals for experimentation
None

Requires code in //chrome?
False

Tracking bug
https://issues.chromium.org/issues/368059226

Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5736024861966336?gate=6381110998204416

This intent message was generated by Chrome Platform Status.
Reply all
Reply to author
Forward
0 new messages