- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sun, 16 Mar 2025 01:35:11 +0000
- To: public-css-archive@w3.org
The spec. now reads like this: > inverted > All pixels within the displayed area have been inverted. > > This value must not match if the user agent has done some kind of content aware inversion such as one that preserves the images. That means authors have no way to detect whether UAs use smart inversion and take counter measures for mistakes. @annevk wrote: > Yeah, that seems bad. Perhaps we can make it a property instead? `auto-invert: on | off` or some such? That gives web developers control, without revealing when it happens. I assume that's meant as feature in addition to the media feature, right? ----- It seems to me we have two options here. 1. Disallow UAs to do smart inversion This makes color inversion predictable but puts the responsibility of correcting incorrectly converted parts completely on authors. 2. Continue allowing UAs to do smart inversion This requires a way for authors to correct parts that got incorrectly handled by the UA. In this case we have four cases: 1. Something got correctly inverted => good 2. Something correctly stayed uninverted => good 3. Something got incorrectly inverted 4. Something incorrectly stayed uninverted The third case could be covered by a property as suggested by @annevk. Question is what to do in the fourth case. I see two solutions to this. Either also cover this via an additional value for the suggested property that forces inversion. Then I'd rather call this property `color-inversion` with the values `auto`, `none`, and `force`. Or it could be covered by a pseudo-class like `:color-inverted` (and target all those _not_ auto-inverted via `:not(:color-inverted)`. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9674#issuecomment-2727114864 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 16 March 2025 01:35:12 UTC