Re: Review of IndieUI User Context

Only one of those modes is “inversion” though: “F1, Standard Inversion” which matches all the other examples below.

The other 5 settings described as “Smart Inversions” are different things entirely. The rest of the settings are features that would/could be covered under other media queries, e.g. the “grayscale” setting should match (monochrome). The “negative gray scale” setting should match (monochrome) and (colors-inverted) 


On Nov 26, 2013, at 8:55 AM, Christophe Strobbe <strobbe@hdm-stuttgart.de> wrote:

> Just a small note with regard to colour inversion: NegativeScreen is an
> open-source application for Windows that supports no less than 11 colour
> inversion schemes: <http://arcanesanctum.net/negativescreen/>. So even
> when colour inversion appears to be binary in many operating systems, it
> clearly needn't be.
> 
> Best regards,
> 
> Christophe
> 
> 
> Am Mi, 13.11.2013, 08:01 schrieb James Craig:
>> Thanks for the review. Responding to the individual points inline.
>> 
>> On Nov 11, 2013, at 10:11 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> 
>>> This is a personal review. It has not been reviewed by the CSSWG.
>>> (...)
>> 
>> 
>>> * 'colors-inverted' should not be a MQ, as the intention of "don't
>>> invert this" should be addressed as a property/value in CSS.
>> 
>> You might be thinking of this in relation to Microsoft’s “high contrast
>> mode” which is not the same as “display inversion.”
>> 
>> A separate concept of “don’t invert this” is insufficient for a few
>> reasons.
>> 
>> 1. Display inversions are usually in low-level display code many steps
>> removed from the rendering engine. If you were to suggest a CSS property
>> for this, it would require the rendering engine to calculate and expose
>> bitmasks of pixel data, potentially each with an algorithm of instructions
>> detailing how to uninvert those pixels, since the rendering engine is not
>> the process doing the inversion.
>> 
>> 2. Second, the colors-inverted media query would be useful for more than
>> just double-inverting foreground content images. I added another example
>> that more clearly illustrates this.
>> 
>> @media (colors-inverted) {
>>   .page {
>>       box-shadow: none;
>>   }
>>   .pagecurl {
>>       background-image: none;
>>   }
>> }
>> 
>> 
>>> (Note
>>> that there are several reasonable ways to "invert" a page, such as RGB
>>> inverting, or lightness inverting. It's not reasonable to assume that
>>> there is only one, author-invertible, way of doing so.)
>> 
>> While it is true that there are other ways to modify colors, the common
>> lexical use of “invert” means the same thing in a majority of OS and
>> common software programs. Other types of color manipulations are possible,
>> but they are not referred to as “inversion” in the common vernacular, and
>> those other types of manipulation can be handled in CSS by other means,
>> such as high contrast mode, user colors, etc.
>> 
>> Some justification that the terms “inverted” and “inversion” are common
>> vernacular meaning this particular type of color modification.
>> 
>> 	Microsoft Windows Magnifier, “Turn on color inversion”
>> 	http://windows7themes.net/quickly-invert-colors-on-windows-8-using-the-magnifier.html
>> 
>> 	Apple iOS, “Invert Colors”
>> 	http://www.apple.com/accessibility/ios/#vision
>> 
>> 	Mac OS X, “Invert Colors”
>> 	http://www.apple.com/accessibility/osx/#vision
>> 
>> 	Android “Inverted Rendering”
>> 	Settings > Accessibility, and find the “Inverted Rendering”
>> 
>> 	Photoshop, “Image > Adjustments > Invert” (also Ctrl+I on Windows, Cmd+I
>> on Mac)
>> 
>> And perhaps most importantly:
>> 
>> 	CSS filter-effects: invert()
>> 	http://www.w3.org/TR/filter-effects/#invertEquivalent
>> 
>> Note that the OS examples are straight pixel inversions, usually in
>> low-level code, sometimes on the GPU. These are not the same as high
>> contrast mode or “night mode” features. The original proposed name for
>> this media feature was “display-colors-inverted” to differentiate that
>> this was a low-level display feature, not a user agent setting.
> 
> 
> 
> -- 
> Christophe Strobbe
> Akademischer Mitarbeiter
> Adaptive User Interfaces Research Group
> Hochschule der Medien
> Nobelstraße 10
> 70569 Stuttgart
> Tel. +49 711 8923 2749
> 
>

Received on Wednesday, 4 December 2013 09:53:47 UTC