- From: Maciej Stachowiak via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jul 2020 23:00:08 +0000
- To: public-css-archive@w3.org
> However, each user agent has their own default form control styling, so the specification of this property will need to be higher level than specific DOM elements. Going over how this might apply to rendering of a wider range of controls as in [this comment](https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-652664697) might help us understand if all of this coming through one property makes sense. For example, Cameron noticed the [highlight color vs accent color issue](https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-652672345). It might help to be even more exhaustive in considering the full range of form controls. For example, one thing to consider is the `<input type=number>` stepper button. There are also colored pieces of form controls that do *not* normally follow the OS accent color. We probably want to avoid including those. Rationale: since accent color is likely to be desirable set across a whole site, that is the common use of similar functionality in apps. So it would be tempting to set it as a rule on `*`, but we wouldn't want unexpected parts of a form control to recolor. -- GitHub Notification of comment by othermaciej Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-652686293 using your GitHub account
Received on Wednesday, 1 July 2020 23:00:10 UTC