elastic
[Form controls] Explore using `accent-color` with default browser inputs
This is tagged as long-term because the support is not great, yet. As of writing only Chromium 93+ and Firefox 92+ support it. And CanIUse is still out of date.
The new accent-color property, applied to the :root allows customizing the main color of certain input controls, right now this includes checkbox, radio, range and progress.
I did a quick sample just changing some styles in Chrome's dev tools to remove our custom div's and applying accent-color.
At least in Chrome, specifically, I think the default styling is close enough to our current aesthetic (maybe even better) that it would make sense to go this path when the support for it gets better.
Another option would be to use the @supports media query to start applying this to browser's that do with falling back to the custom one if they don't. But this could be tricky to maintain.
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.
❌ Per our previous message, this issue is auto-closing after having been open and inactive for a year. If you strongly feel this is still a high-priority issue, or are interested in contributing, please leave a comment or open a new issue linking to this one for context.
👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.
Closing this as not planned - several designers have weighed in on #7819 and the consensus is the loss of consistency cross-browser and loss of control over fidelity is not preferred at this time/with our current theme.