- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jul 2020 23:50:25 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Allow specifying the "accent color" of a form control element`. <details><summary>The full IRC log of that discussion</summary> <dael> TOpic: Allow specifying the "accent color" of a form control element<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5187<br> <dael> chrishtr: Form controls are styled and painted in UA specific way in all browsers<br> <dael> chrishtr: There tends to be a concept of an accent color used to indiacte checked or marked state of form controls.<br> <dael> chrishtr: UAs pick a default color for that that's consistent in page. There are also OS settings on some OSs to change accepnt color which is respected by some browsers.<br> <dael> chrishtr: COlor might conflict with brand of site, like site with orange theme but checkboxes are blue<br> <dael> chrishtr: Proposal is to ahve css property which says form controls should use this color as basis of accent color when painting form control<br> <dael> Rossen_: Opinions on this?<br> <tantek> the other big use-case is for sites that want to make "darker" versions of form controls that match their site styling, similar to scrollbar colors<br> <hober> q?<br> <dael> fantasai: Main concern is it's not clear what accent color is used for. B/c that it's nto clear what's expected contrast between that, text, and background.<br> <tantek> +1 agree with fantasai, needs to be predictably specified so it makes sense across OSs and devices<br> <dael> fantasai: Concern people will choose colors that are good on some OS but won't contrast with background enough in other rows. For example a select multiple it needs to contrast with text. But on a selected checkmark it's background<br> <dael> fantasai: Understand what you're trying to do but concerned we won't get something robust across browsers<br> <tantek> needs to be sufficiently predictable across browsers<br> <dael> florian: Can we split into foreground and background or does that not generalize well<br> <dael> myles: We had internal discussion and general feeling is good for web in general. Not sure mech to expose. We have a general idea good to style lots of form control aspects. Good to do in general not just one piece. In general feel this has value for web.<br> <tantek> +1 myles that's a good summary<br> <fantasai> tantek, that use case is handled by the 'color-scheme' property fwiw<br> <fantasai> tantek, https://www.w3.org/TR/css-color-adjust-1/#preferred<br> <dael> chrishtr: Re: general styling point. Agree that there are other things devs wish to style and hopefully can. This one seems to be simple and common and immediately solves a specific conern. THat's why I think do it as a one-off for the moment and general in future<br> <Rossen_> q?<br> <jensimmons> q+<br> <tantek> fantasai, not talking about not dark mode. hence I said darker deliberately<br> <hober> q?<br> <dael> florian: General will take time. Seems most of time accent color is related to backgrou,d but not always. If it's background or foreground matters. Having the pair would be a step which could make sense. There can be many aspects of form control we can do later. Knowing if your'e in foreground or background matters.<br> <dael> heycam: Ignoring select multiple issue which might nto be accent color all other colros are contrasting separately. For checkbox and radio you'd got icon inside which authors can't control. I think for most cases where accent color can be changed any contrasting color can be painted by UA.<br> <dael> jensimmons: Has anyone working on open UI on the call? I know a lot of work has gone into form controls and what it means to style them<br> <dael> myles: On iOS there's no concept of the accent colors. Whatever is in spec needs affordences for OS where it doesn't apply<br> <Rossen_> q?<br> <Rossen_> ack jensimmons<br> <dael> florian: If we look at range of historical OS to get diversity the buttons were a shade of blue. If that was still the fashion accent color wold be there and it's very background-y<br> <florian> https://66.media.tumblr.com/e0c02215356306ee52298451ac25685e/tumblr_o5a0h4UIDN1v0jfsto2_1280.png<br> <florian> http://pcdesktops.emuunlim.com/pictures/skins/wb/macosx-aqua-bjb.gif<br> <dael> chirsh: Answering jensimmons, I'm working with gregwhitworth and others on longer term project for form controls. I don't know if enought o discuss here. In general I think compat. I don't think enough to say about OpenUI to clarify<br> <dael> Rossen_: Is there a resolution you're looking for?<br> <dael> chrishtr: I'm hoping to get to agreement on name and set of text what's it's supposed to be for UA and says UA should make sure sufficent contrast and only where it makes sense<br> <dael> fantasai: Fine to try and draft language. Requires more release to make so it works on a variety of OSs. I'm a little skeptical this will work but understand we want it. I'm concerned about having it work for all OSs.<br> <dael> fantasai: If we can show that would be the case across current and past OSs and there's a reasonable interpretation for all the OS/browser combos I would feel more comfortable moving forward<br> <jensimmons> +1 to what fantasai said<br> <dael> chrishtr: Hearing general support but need mroe research to understand compat as well as foreground/background comments<br> <dael> fantasai: I think we should do that evaluation in GH. Might be right design, but might be diversity of form controls requires something different.<br> <tantek> we're also looking preliminarily at a more longer term project for form controls as well, if existing work is happening in the open, please share that in CSSWG! Thanks!<br> <dael> chrishtr: We'll come back with more concrete proposal<br> <dael> florian: What I'd liekt os ee in research is wide variety of form control and show form controls is always background or neither. If it's in foreground sometimes we need to split it up.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5187#issuecomment-652700033 using your GitHub account
Received on Wednesday, 1 July 2020 23:50:27 UTC