- From: Jonas Sicking <jonas@sicking.cc>
- Date: Mon, 2 Dec 2013 20:52:09 -0800
- To: Mounir Lamouri <mounir@lamouri.fr>
- Cc: Webapps WG <public-webapps@w3.org>
On Nov 26, 2013 9:17 AM, "Mounir Lamouri" <mounir@lamouri.fr> wrote:
>
> Hi,
>
> I got some requests from different organizations to add the ability to
> lock to the 'current' orientation in the Screen Orientation API.
>
> >From Javascript, that would allow writing
> window.screen.lockOrientation('current');
> instead of
> window.screen.lockOrientation(window.screen.orientation);
> Basically, a syntax sugar.
I don't care too much about this one. But syntax sugar for something
that isn't really a very common operation seems excessive. Unless
locking to current is something we really want to encourage?
The strongest argument that I can think of is that it would be nice to
keep the manifest spec and the API spec for orientations aligned. So
if we think this is common enough that apps will want to use it in the
manifest, then allowing it in the API too would make sense.
> >From the manifest, writing the following
> 'orientation': 'current',
> would allow locking the application to the orientation it is loaded in
> at startup.
> It is a tiny use case but it seem that there are apps out there doing
> that (like the iOS Task Switcher, I was told).
The iOS task switcher isn't really a normal app. Are there other apps
that are known to do this?
/ Jonas
Received on Tuesday, 3 December 2013 04:53:07 UTC