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

Sounds reasonable. I think the main things that are missing are
explanations of the knock-on effects of Device Adaptation (and the meta
viewport tag).

For example the CSSOM View <> module
claims that all its dimensions are in CSS
But if you look at what mobile browsers return for something like
screen.width, they either return Device Independent Pixels (DIPs) or
physical device pixels. It's only for things like window.innerWidth that
mobile browsers actually return a value in CSS pixels. Now, returning DIPs
does in fact best match the intent of the spec for screen.width
(indeed the definition
of a CSS pixel <> is
actually the definition of a DIP, and they used to be the same thing until
pinch zoom and viewports made them scale independently); but the CSS specs
need to accept that there are more kinds of pixels than there used to be,
and fix these ambiguities, if we want mobile browsers to converge on a
single behaviour.

On Wed, Jun 5, 2013 at 2:59 PM, Kenneth Rohde Christiansen <> wrote:

> I think it should be. You think anything is missing?
> Kenneth
> On Wed, Jun 5, 2013 at 3:51 PM, Simon Pieters <> wrote:
>> On Wed, 24 Apr 2013 13:00:48 +0200, Kenneth Rohde Christiansen <
>> kenneth.r.christiansen@intel.**com <>>
>> wrote:
>>  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.
>> There's currently**
>> device-adapt/#dom-interfaces<>
>> Is that sufficient?
>> --
>> Simon Pieters
>> Opera Software
> --
> Kenneth Rohde Christiansen
> Senior Engineer, WebKit, Qt, EFL
> Phone  +45 4294 9458 / E-mail kenneth at
> ﹆﹆﹆

Received on Wednesday, 5 June 2013 14:35:42 UTC