W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: Charter addition proposal: screen orientation lock

From: Mounir Lamouri <mounir@lamouri.fr>
Date: Mon, 30 Jan 2012 18:32:46 +0100
Message-ID: <4F26D43E.8000605@lamouri.fr>
To: public-webapps@w3.org
On 01/30/2012 03:57 PM, Kenneth Rohde Christiansen wrote:
>     Also, I do not think the specifications should restrain the conditions
>     in which the screen orientation lock can happen. At least not at the
> It doesn't have to do that, but it could point out that UAs might want
> to restrict the orientation lock to certain situations. But I think we
> might end up with most browsers acting differently and causing
> fragmentation, thus some recommendation should be fine and can be
> ignored if the UA seems fit.

This is what I meant by "not a MUST", so I guess we agree :)

>     Linking screen orientation and fullscreen like that seems a bad idea.
>     Basically, you can only lock and never reads. In addition, how do you
>     handle an iframe requesting fullscreen?
> We need this to be tied together in some way, so that it is possible to
> click on say, a video element and have to animate entering fullscreen
> and rotating at the same time. Doing these two transitions separately,
> would look pretty bad (at least animated).

Sounds interesting. Maybe we could extend the fullscreen API later.
However, we shouldn't force authors to use the fullscreen API to lock
the screen.

Received on Monday, 30 January 2012 17:33:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:38 UTC