- From: Christoph Päper via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Dec 2019 22:42:14 +0000
- To: public-css-archive@w3.org
Crissov has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color][css-ui] Better Fallback for outline-color: invert; and Introduce Elsewhere == The support for [`outline-color: invert`](https://drafts.csswg.org/css-ui-3/#valdef-outline-color-invert) is very limited #423, because, as I understand it, it is complicated to achieve the effect with current technology while it used to be simple when fewer layers of abstraction stood between hardware and browser. CSS-UI therefore allows browsers to ignore the value altogether. Can we perhaps do a little better? I propose that browsers should, instead, fall back, to inverting the computed value of the `background-color` property. In some simple cases with the same plain background, this will actually yield the expected visual result. With this convention in place, `invert` might even become useful as a keyword for other `*-color` properties, but, to avoid cycles, not for `background-color` itself and thus not for the [`<color>`](https://drafts.csswg.org/css-color/#color-type) type. - `color` - `border-color` - `stroke-color` Plans and proposals for more sophisticated color modifications should not be affected by this. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4611 using your GitHub account
Received on Tuesday, 17 December 2019 22:42:16 UTC