- From: Mason Freed via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jul 2020 21:52:30 +0000
- To: public-css-archive@w3.org
> What's the intended scope of `accent-color`? Is it just color of the checked state of radio buttons and checkboxes? If so, then the name seems inappropriately broad. If it's more things than that, then that may shed light on the name, and whether it should all be one property. Ideally, the `accent-color` property can be specified to apply to all form controls, as appropriate. The appearance and styling of form controls is (deliberately) not well-specified, so it might be tough to avoid somewhat vague language here. However, I think the concept is reasonable. For example, in Safari, the system Accent Color setting affects: - The "background" color for `<input type=checkbox>` - The "background" color for `<input type=radio>` - The activation "button" for `<select>` - The activation "button" for `<input type=text list=datalist>` - The highlighted row of `<select multiple>` - The active state of `<button>` All of the above seem to make sense as a usage of the accent-color. In Chrome, I could also see adding to the above list: - The shaded portion of the `<range>` control - The clear ('X') button on several controls such as `<input type=search>` Again, the idea is to control the currently-uncontrollable colors of form elements just a bit better. Our hope is that the more broad Open UI type improvements in stylability will give even better control over all pieces of these controls. But in the meantime, this `accent-color` proposal will alleviate many very real, very [painful](https://bugs.chromium.org/p/chromium/issues/detail?id=1091531) developer problems with the existing control styling. -- GitHub Notification of comment by mfreed7 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-652664697 using your GitHub account
Received on Wednesday, 1 July 2020 21:52:32 UTC