Improve <input type="color">
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
From what I saw, most developers prefer third-party color pickers (react-color, colorPicker etc.) over native <input type="color"> for many reasons.
Off the top of my head:
- switching between various color spaces: HEX, RGB, HSV, HSL, etc.
- switching between various UIs: wheel, palettes, etc.
It would be also really nice to:
- enable/disable color components (e.g. enable A for RGB)
- limit
minandmaxvalues for color components (e.g. limit L in HSL) (BTW, what about alsostepattribute?)
Something like:
I've also found that pattern, required, readonly attributes don't work for <input type="color"> in Chromium, but disabled works. @domenic cc.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue proposes broad changes to the native control, including color spaces, UI options, component limits, step handling, and validation attributes, but names no files or tests. Start by narrowing the desired scope and reviewing the Chromium behavior mentioned; done requires an agreed design or specification change with corresponding platform behavior defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100