- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Oct 2020 16:55:28 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `accent-color`, and agreed to the following: * `RESOLVED: adopt accent-color as a hint to the UA, with requirements on contrast` * `RESOLVED: Mason Freed added as UI 4 editor` <details><summary>The full IRC log of that discussion</summary> <astearns> topic: accent-color<br> <TabAtkins> masonfreed: Summary is I closed the "interopability thread" - question I was trying to ask was whether we wanted precise control over where accent colors should go on a control<br> <TabAtkins> masonfreed: Think I got the answer I needed - we dont' want to do so.<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/5187<br> <TabAtkins> masonfreed: Majority opinion seems to be that we want this to be more of a hint to the UA - "accent-color: purple" means "use purple on this control if you can if it makes sense".<br> <TabAtkins> masonfreed: Not "put this purple on the checkbox background", more of a hint instead<br> <Rossen_> q<br> <TabAtkins> masonfreed: So I'd like to get a reoslution from the grou pon this direction<br> <TabAtkins> q+<br> <jensimmons> q+<br> <fantasai> sgtm<br> <florian> q+<br> <Rossen_> ack TabAtkins<br> <fantasai> TabAtkins: I'm not sure this is exactly the right direction, fine with it as long as we adopt something like what fantasai said, where we require the UA's chosen colors contrast appropriately with the accent-color<br> <fantasai> TabAtkins: UA can't put black on black ifyou specify accent-color:black<br> <fantasai> TabAtkins: With that, sounds fine<br> <fantasai> Rossen_: you can't ignore the accent color?<br> <fantasai> fantasai: can always ignore it...<br> <TabAtkins> jensimmons: I think how Mason described it is good and realistic<br> <Rossen_> ack jensimmons<br> <fantasai> jensimmons: I think the way Mason described is really good, more realistic to where we are<br> <fantasai> jensimmons: more time to solve the problem of robus styling<br> <TabAtkins> jensimmons: Allows us to give authors something useful and gives us time to solve the problems more robustly<br> <TabAtkins> florian: Roughly in line with all that. As long as the hint involves the requirement that contrast must work.<br> <TabAtkins> florian: Don't think we have a resolution on one vs many colors, but we can decide that later<br> <Rossen_> acj florian<br> <TabAtkins> florian: I think there is an appetite for precise control, but that requires a more robust solution. Should od that too, but shouldn't conflate with this.<br> <Rossen_> ack florian<br> <TabAtkins> Rossen_: Taking the lack of queue as meaning we've said everything we need. Objections?<br> <TabAtkins> proposed resolution: adopt accent-color as a hint to the UA, with requirements on contrast<br> <tantek> I think we're ok with that too<br> <TabAtkins> RESOLVED: adopt accent-color as a hint to the UA, with requirements on contrast<br> <TabAtkins> masonfreed: We probably need to discuss the 1 vs many colors question later<br> <TabAtkins> Rossen_: yes<br> <TabAtkins> fantasai: I think we should put this into UI 4, should we let the editors put that in, and discuss 1 vs many colors separately?<br> <TabAtkins> astearns: Would Mason like to become an editor?<br> <TabAtkins> masonfreed: "want" is strong, but I'm willing to do it<br> <TabAtkins> florian: Happy to have help<br> <TabAtkins> fantasai: There is proposed text already<br> <TabAtkins> Rossen_: Objections to adding Mason as UI 4 editor?<br> <TabAtkins> RESOLVED: Mason Freed added as UI 4 editor<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-715458733 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 October 2020 16:55:30 UTC