W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: Next step for DAP Ambient Light Events

From: Marcos Caceres <w3c@marcosc.com>
Date: Fri, 31 Aug 2012 12:56:29 +0100
To: "fremycompany_pub@yahoo.com" <fremycompany_pub@yahoo.com>
Cc: Doug Turner <dougt@mozilla.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, CSS WG <www-style@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>, Dzung D Tran <dzung.d.tran@intel.com>
Message-ID: <EAA017D92E034296A84F805E7E001A82@marcosc.com>


On Tuesday, 28 August 2012 at 15:53, fremycompany_pub@yahoo.com wrote:

> This problem was already discussed in the CSS working group and we decided that we would support keywords only for the special cases where the screen brightness can’t be adjusted to the ambient lighting.
>  
> We therefore concluded we would support only three modes:
>  
> - high-contrast (black on white) for when the user agent detects the screen is washed (in a too bright direct sunlight).
>  
> - normal (usual mode) for when the user agent detects the screen is able to adapt his brightness to the surrounding environment.
>  
> - high-contrast (white on black) for when the user agent detects the surrounding environment is very dark (tunnel, night...)
>  
> Additionally, those modes would also be used by visually-impaired people like it’s done in IE10 at this time.
>  
> This should be a good approach, isn’t it?


This sounds reasonable, but can you provide an example how the above three are used? Also, do you have a link to the IE 10 high-contrast modes?   

  

   
--  
Marcos Caceres
http://datadriven.com.au
Received on Friday, 31 August 2012 11:57:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:59 GMT