Re: Orientation lock still needed?

To save others the confusion of "how does the API expose locking?":

On Wed, Feb 15, 2012 at 4:21 AM, Mounir Lamouri <mounir@lamouri.fr> wrote:

> On 02/15/2012 04:29 AM, Tobie Langel wrote:
> >> In the Screen Orientation API draft, I don't see any references to
> >> locking. Is this by design?
> >
> > It's in the abstract:
> >
> > "The Screen Orientation API's goal is to provide an interface for web
> > applications to be able to read the screen orientation state, to be
> > informed when this state changes and to be able to lock the screen
> > orientation to a specific state."
> > --http://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html
>
> I only wrote the reading part for the moment because there are still
> some discussions in Mozilla's WebAPI mailing list [1] about the locking
> part. When the specification draft will be complete, I will send a
> message here.
>
> [1] https://www.mozilla.org/about/forums/#dev-webapi
>
> --
> Mounir
>


On Wed, Feb 15, 2012 at 8:35 AM, Boaz Sender <boaz@bocoup.com> wrote:

> On Wed, Feb 15, 2012 at 4:24 AM, Paul Bakaus <pbakaus@zynga.com> wrote:
>
>> Hi everybody,
>>
>> Meta viewport and orientation lock are entirely separate feature sets.
>> Orientation lock is very much needed, and I have good news: It has been
>> added to the WebApps charter:
>> http://www.w3.org/2008/webapps/wiki/CharterChanges
>> (http://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html). I
>> don't think people agree on the API yet, but at least, everybody agrees
>> it's needed.
>>
>
>
> Sorry Vincent, it looks like I got confused. The JS API for screen
> orientation state and locking is what we need.
>
> I've also heard talk of a CSS based approach, not sure what that looks
> like, or if it makes sense. I prefer a JS interface.
>
> Thanks for cleating that up Paul/Erik!
>
> --
> Boaz Sender
>
>