- From: Robin Berjon <robin@berjon.com>
- Date: Mon, 28 Nov 2011 17:50:13 +0100
- To: Dominique Hazael-Massieux <dom@w3.org>
- Cc: public-device-apis@w3.org
Hi Dom, On Nov 28, 2011, at 12:10 , Dominique Hazael-Massieux wrote: > Part of the discussion during TPAC was that particular item might be > better served by a CSS media query feature rather than an JavaScript API > — at least, the use cases that involved adapting e.g. the colors of the > user interface would be more logically served via such an approach. That certainly seems to match the use cases heard to date better than an API would. What's more, even if there exists the need for an API because we uncover other UCs, usage from CSS seems rather natural and so I would see justification for having both. > This would mean adding a "ambientlight" feature with min/max prefixes, > that would take values in SI lux units. > > <link rel="stylesheet" media="screen" href="default.css"> > <link rel="stylesheet" media="screen and (min-ambientlight: > 30000)" href="high-contrast.css"> This looks pretty good to me. > If the group thinks that's a reasonable approach, DAP could propose to > start a joint WD with the CSS WG. We actually probably don't need to set up joint work (not that I'm against it). The WebApps WG wrote its own media feature (view-mode, http://www.w3.org/TR/view-mode/) without making it joint. We would naturally need to have the CSS WG review it, but in my experience they tend to be pretty diligent about that, especially if we ping them early on. The real question is: do we have an editor? :) -- Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 28 November 2011 16:50:50 UTC