- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Jan 2021 17:35:50 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-ui-4] Use of accent color outside of form control elements`, and agreed to the following: * `RESOLVED: UAs may use an accent-color outside of form controls at their discretion` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-ui-4] Use of accent color outside of form control elements<br> <fantasai> s/minimum/minimum -- and anything else that might affect it in the future/<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5657<br> <dael> florian: Introduced accent-color to let you change it when there is one. Mostly talked about it as form controls. But there are other things that might be colored link scrollbars or the selection color or an outline color.<br> <dael> florian: Are these supposed to be influenced? I'd say yes but didn't discuss it explicitly<br> <dael> leaverou: I think they should and authors should be able to access this property if there isn't already<br> <dael> florian: You mean default?<br> <dael> leaverou: If you override can authors use in other properties?<br> <dael> florian: Author sets it<br> <dael> leaverou: If I set accent-color is there a keyword like currentColor?<br> <dael> florian: No<br> <dael> leaverou: Should be<br> <dael> florian: Can't you set a variable?<br> <dael> leaverou: Can but variable is a contract between values but accent-color is a global<br> <dael> chris: Seems you should do it like this, but it's not a single author that writes stylesheet<br> <dael> florian: Sounds like a separate issue. Can you file a new issue? It's interesting<br> <dael> leaverou: Yes<br> <dael> florian: So are we going to apply this to scrollbars, outlines, all things that could be colored.<br> <dael> fantasai: I think UA should be allowed to do so. We need to be clear about definition as to what an accent-color is. Scrollbars mostly don't have accent-colors. accent color is the color that stands out. Inthat light I think it makes sense to allow UA to use it any place where it derives a color, but I think it should be a may so UA can decide if it's able<br> <dael> chris: This is behind the scenes magic?<br> <jensimmons> q+<br> <dael> florian: Yeah b/c we don't know how UA builds these in the first place. To extent they use one.<br> <astearns> ack jensimmons<br> <dael> jensimmons: Thinking about setting universal accent for my whole site as an author it feels like not knowing all details of where it shows in form control makes sense to me. Having whole scrollbar that color is too much<br> <dael> florian: Wouldn't be, though<br> <dael> jensimmons: If scrollbar still have arrow it could color that<br> <dael> florian: Not adding colors where they aren't. But if UA is using a blue accent you ask to switch to purple<br> <dael> fantasai: I think we should give an example in spec as to what effect it would have<br> <fantasai> s/would have/would have to set it on the root and letting it inherit through/<br> <dael> florian: Example is in macOS you can change accent color of whole system. You highlight color for selection changes. And other places<br> <dael> leaverou: Is UA allowed to use varations of it? Can UA make it lighter or darker?<br> <dael> florian: It's speced that yes.<br> <dael> leaverou: Okay<br> <fantasai> https://drafts.csswg.org/css-ui-4/#widget-accent<br> <dael> florian: Main cases is to maintain contrast or b/c if you think of aqua mac OS with gradients you don't want to substitute a gradient with a flat color.<br> <fantasai> "The UA should use the specified accent-color to draw whichever parts of the element’s control(s) would have otherwise been styled with an accent color. The UA must maintain contrast for legibility of the control, and in order to do so may adjust the luminance or brightness of the color or make color substitutions in other parts of the control (e.g. switching an overlaid glyph from using color to using<br> <fantasai> background-color). It may also generate variations of the color for gradients etc. to match the control to platform conventions for the use of the accent color."<br> <dael> astearns: Hearing yest we should allow UAs to use accent color outside of form controls. Leave to UA if it's appropriate<br> <dael> smfr: Confused about how relates to system colors. Do we want to prevent this from leaking?<br> <dael> TabAtkins: accent-color isn't user privacy<br> <dael> smfr: Author spec, right.<br> <dael> jensimmons: Makes a lot of sense to work outside of form controls. Want it to be up to browser or vendor of how it works. Should have clear language around that this is for accents, not just coloring all the bits. These are things that are true accent colors. Would allow authors to set univerally and not have unintended consiquences.<br> <dael> fantasai: Spec does have wording. If you want to suggest improvements give it a look<br> <dael> astearns: Risk of unintended consiquences if user has accent-color and likes what Safari does but doesn't check Chrome. But b/c nature of feature this is just a hint which the browser can do what they want. That possible mis-match comes with territory<br> <dael> florian: Examples from leaverou and jensimmons are reasonable. They're intended to be covered in spec text. Pelease give a look and feedback<br> <jensimmons> cool, yes, fantasai & florian on taking a look at what you've already done on this. Thank you.<br> <dael> astearns: Prop: UAs may use an accent-color outside of form controls at their discression<br> <dael> RESOLVED: UAs may use an accent-color outside of form controls at their discretion<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5657#issuecomment-768451736 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 January 2021 17:35:52 UTC