- From: <bugzilla@jessica.w3.org>
- Date: Sun, 16 Mar 2014 08:23:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25054
Bruno Racineux <bruno@hexanet.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruno@hexanet.net
--- Comment #4 from Bruno Racineux <bruno@hexanet.net> ---
(In reply to Mounir Lamouri from comment #0)
> I think the API should probably not be exposed if the device do not allow
> orientation changes. There isn't much value in reading the orientation if
> the orientation can't change.
The computer 'device' (if that's what you mean) should be irrelevant. That API
is not particularly targeted for mobile devices. It has a broader 'screen'
context.
> If it is only a presentation problem, CSS solves that already with media queries.
No. Media queries don't match for all devices, and we shouldn't assume so.
The orientation media query looks at the viewport (in relation to the window
width and height, which only solves most modern/mobile or fullscreen view
cases), not the screen. The screen orientation can be used to account for that
difference.
In IE snap-mode for example, you can get a 'portrait' media query on a
'landscape' screen rotation. So the Screen Orientation has a value, for
alternatives contexts.
(In reply to Olli Pettay from comment #3)
> I think it is up to the implementation to decide what to do.
> What is the harm to have the API always there?
>
> Also, you can change the screen orientation even on desktop.
Indeed, there are large monitors that pivot from portrait to landscape.
And some people have stations with both a vertical and a horizontal screen.
Additionally the screen on a fixed Windows touch laptop can be locked to
portrait at the system level.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 16 March 2014 08:23:42 UTC