Re: [screen-orient] why not provide at CSSOM API to CSS Device Adaptation instead?

Hi there,

CSS Device Adaptation should hopefully be enabled on all browsers (desktop
and mobile) unlike the viewport meta tag, which cannot be enabled on
desktop browsers easily as many desktop sites actually comes with a
viewport meta tag which is ignored. Having that not being ignored breaks
the sites.

MS already enabled a subset of the CSS Device Adaptation spec in IE10

I support adding some CSSOM API's for CSS Device Adaptation, but I would
not do so for the viewport meta tag, which has its share of issues. I would
also like the CSS Device Adaptation, orientation lock and Fullscreen to
integrate. Especially it would be nice to click on an element in portrait
and have it go fullscreen in landscape mode and lock, all with a nice


On Wed, Apr 24, 2013 at 12:13 PM, Tobie Langel <> wrote:

> Hi,
> Screen orientation lock is critical to a whole set of mobile games
> (especially those which rely on the accelerometer to control the gameplay).
> It's great that it is now considered for specification and implementation.
> I had collected some use cases a while back[1], some of which led to
> use-cases[2], requirements[3] and suggestions[4] in the Coremob report.
> While some of the original use cases required dynamically modifying
> orientation lock (e.g. the Game within a game experience[5]), key use cases
> simply require a declarative, page-wide setting, as described by David
> Bruant on the WHAT WG mailing list[6].
> The current proposal[7] only targets the dynamic setting through a JS API
> and leaves the more declarative approach to other specs[8]. It mentions the
> Web Application Manifest Format and Management APIs[9] and CSS Device
> Adaptation[10].
> Now, CSS Device Adaptation, as used in the Viewport META element[11] is
> ubiquitous on mobile. It seems like a natural fit for a declarative
> orientation lock, so much so that it's already specified in the spec[12].
> However, the syntax to dynamically read or modify the Viewport META
> element is cumbersome and error prone (you're talking document.cookie-like
> string splitting/concatenation with unspecified separators, etc.[12]).
> Instead of providing a dedicated API to cater strictly for the screen
> orientation lock use case, wouldn't it make more sense and be more
> consistent to provide a CSSOM[14] API for the whole Viewport META element,
> and use matchMedia listeners[15] instead of orientationchange events?
> This would allow declarative setting through the Viewport META element,
> dynamic modification through the CSSOM API, and event handling through the
> matchMedia interface, all of which are well known and commonly used by
> developers.
> Thanks for your time.
> --tobie
> ---
> [1]:
> [2]:
> [3]:
> [4]:
> [5]:
> [6]:
> [7]:
> [8]:
> [9]:
> [10]:
> [11]:
> [12]:
> [13]:
> [14]:
> [15]:

Intel Denmark Aps
Langelinie Alle 35, DK-2100 Copenhagen
CVR No. 76716919

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Received on Wednesday, 24 April 2013 11:01:39 UTC