- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Oct 2019 16:29:31 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `text system color conflicts with background-clip`, and agreed to the following: * `RESOLVED: Rename text keyword to CanvasText` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: text system color conflicts with background-clip<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4465<br> <dael> TabAtkins: When we introduced the set of new good system colors we names one text. Means in BG shorthand supplying color text conflicts with clip of text.<br> <dael> TabAtkins: It's goingt o be a problem when we unprefix<br> <dael> TabAtkins: Proposal is rename text to canvas-text which matches other pairs. canvas-text is unambig and resolves situation<br> <dael> TabAtkins: And I dont think text was an old word<br> <dbaron> s/canvas-text/CanvasText/<br> <dael> fantasai: Anyone shipped?<br> <dael> TabAtkins: No. FF wanted to but ran into grammar<br> <dael> Rossen_: Same for us<br> <dael> fantasai: In favor. Makes sense and less likely to conflict<br> <dael> leaverou: Agree<br> <dael> myles: Worth tryign to come up with system to discover these ambig automatically?<br> <tantek> that's what CR is for, right? ;)<br> <dael> TabAtkins: Sounds like it would be valuable, but a bunch of work<br> <dael> AmeliaBR: TabAtkins write a bikeshed extension for all grammars ^-^<br> <dael> Rossen_: Objections to rename text to CanvasText?<br> <dael> smfr: I think WK has shipped text since KHTML days. Someone might be using it in the wild<br> <dbaron> Such a tool wouldn't have caught this because we haven't actually written the grammar for the background shorthand in backgrounds level 4.<br> <dael> TabAtkins: Really? Never appeared in list from Color 3. I didn't realize it was live<br> <dael> Rossen_: Sounds like only in WK<br> <dael> smfr: Don't know if Chrome removed it post-branch<br> <dael> Rossen_: I don't see in Chrome keywords<br> <dael> smfr: Other comment is I thought background clip text was being replaced by something in fill and stroke?<br> <dael> TabAtkins: Replaced but can't remove<br> <TabAtkins> Looks like Chrome has removed it: <body style="background-color: red; background-color: text;"> is red.<br> <dael> AmeliaBR: Shipped in FF unprefixed. One thing is issue is allow background clip text, but don't allow in the shorthand. More complicated to impl and spec vs changing the color keyword. If there is compat issue we want to know what the impact is<br> <dael> chris: Possible to have old text value as an alias so it works in the longhand but not allwoed in shorthand<br> <tantek> what about WindowText? noticed that's in the MDN docs: https://developer.mozilla.org/en-US/docs/Web/CSS/color_value<br> <dael> TabAtkins: Possible, but complexity we like to avoid if we can<br> <leaverou> UIText may work too<br> <dbaron> this is presumably different from WindowText since WindowText was a CSS 2.1 value<br> <TabAtkins> tantek, window/windowtext aren't a pair we chose to use<br> <tantek> cool TabAtkins, I guess we need to update MDN<br> <dael> fantasai: I think we should rename this. It's better usability and less complex. If we need to support a text keyword that means the same thing if we need it for compat we've got a bunch of mappings we have to do. WE should check and see if need to address. If not maybe WK drops. If so we figure out a way to handle<br> <dbaron> CSS 2.1 list is at https://www.w3.org/TR/CSS21/ui.html#system-colors<br> <dael> fantasai: AS far as system colors we're promoting CanvasText makes sense as will have less problems going forward<br> <dael> smfr: I'm okay trying to rename<br> <AmeliaBR> s/thing is issue/thing suggested in the issue/<br> <tantek> FYI Moz also has -moz-default-color User's preference for the text color.<br> <dael> Rossen_: Objections to renaming?<br> <dael> RESOLVED: Rename text keyword to CanvasText<br> <TabAtkins> tantek, windowtext is one of the deprecated colors; just not one of the good ones we're using for forced colors. MDN is fine.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4465#issuecomment-547994485 using your GitHub account
Received on Wednesday, 30 October 2019 16:29:33 UTC