- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Apr 2019 16:43:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Support high-contrast/dark mode colors`, and agreed to the following: * `RESOLVED: add the original list of colors from TabAtkins and fantasai as well as ones by smfr and ActiveLinkText` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Support high-contrast/dark mode colors<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3804<br> <dael> TabAtkins: Working from the presentation of Rossen_ and melanierichards. fantasai and I put together prop for high contrast stuff in CSS. Defining system colors, some exist some new, that map to categories from Rossen_ and melanierichards<br> <dael> TabAtkins: Only addition is a visited link color in addition to normal and that's because it's already in system colors. MS could set to same color if they want.<br> <dael> TabAtkins: Idea being is we adapt MS rules for how to apply that says you apply these system colros whereever nec. THere's a MQ that says these are on and you may want to adjust your styles.<br> <dael> fantasai: Resolved on that earlier, need to add the colors. Resolved on the MQ and properties. This is about making changes to CSS color L4 to un-deprecate a subset of the system colors and add a couple of new ones<br> <dael> fantasai: New is page background, scrollbar, link text, visited link text<br> <dael> dbaron: Active link text?<br> <dael> fantasai: Might need to add that, yes<br> <TabAtkins> Canvas* (we'd have liked to call this “Background” but that's already used for something else)<br> <TabAtkins> Text*<br> <TabAtkins> LinkText*<br> <TabAtkins> VisitedText*<br> <TabAtkins> Highlight<br> <TabAtkins> HighlightText<br> <TabAtkins> GrayText (could be aliased to InactiveText or DisabledText for clarity)<br> <TabAtkins> ButtonFace (could be aliased to Button for consistency)<br> <TabAtkins> ButtonText<br> <dael> AmeliaBR: Couple other suggestions in thread of colors used in UA stylesheets. Some of which not named<br> <dael> fantasai: Discussion about adding field values for text inputs. I don't have a strong opinion on that. Wanted to make sure got minimum set MS was using in high contrast mode. If WG wants to add field and field text can add<br> <TabAtkins> Looks like additional stuff is just "Field" and "FieldText"<br> <dael> Rossen_: High contrast PoV your set of colors maps to what's required. I don't have strong pref for additional ones, I don't know use cases. I guess people creating own components and want closer to current system controls sounds reasonable.<br> <AmeliaBR> and ActiveLinkText<br> <dael> Rossen_: Want to hear from rest of group<br> <fantasai> or ActiveText<br> <dael> Rossen_: Taking silence as supportive<br> <dael> Rossen_: Prop: un-deprecate or add the list above<br> <dael> fantasai: * is added<br> <dael> AmeliaBR: IRC discussion mentions the others<br> <dael> fantasai: ActiveLinkText and Input field background and foreground color<br> <dael> fantasai: WE pulled old names for those, don't know if they're nec. I think we at least need to minimum set for MS high contrast. If people want to add others I"m fine<br> <tantek> aside: see more Link related colors here: https://www.w3.org/TR/2002/WD-css3-color-20020418/#css3-user<br> <dael> Rossen_: Objections to add the original list of colors from TabAtkins and fantasai as well as ones by smfr and ActiveLinkText<br> <dael> RESOLVED: add the original list of colors from TabAtkins and fantasai as well as ones by smfr and ActiveLinkText<br> <dael> fantasai: On activeLinkText we have LinkText and VisitedText. We went shorter version of names b/c match selector<br> <dael> Rossen_: Shorter makes sense<br> <tantek> aside: (cont'd) which were dropped (not just deprecated) from the REC: https://www.w3.org/TR/css-color-3/#css2-system<br> <dael> AmeliaBR: There's already ActiveButtonText so that' sonly confusion<br> <dael> AmeliaBR: If it needs to be clear ActiveText is color for active links<br> <dael> fantasai: Active button can be own thing<br> <dael> Rossen_: Okay. Previous resolution stands<br> <dael> Rossen_: Resolution is ActiveText not ActiveLinkText<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3804#issuecomment-486325470 using your GitHub account
Received on Wednesday, 24 April 2019 16:43:27 UTC