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

Re: CfC Re: Charter addition proposal: screen orientation lock

From: Vincent Scheib <scheib@google.com>
Date: Wed, 15 Feb 2012 10:09:45 -0800
Message-ID: <CAK-EfXkmS7Rk=d-Z9pn0nB+=Xrn1xc_EjiBeiPm3Ycj9RQWSgg@mail.gmail.com>
To: Paul Bakaus <pbakaus@zynga.com>
Cc: Mounir Lamouri <mounir@lamouri.fr>, "public-webapps@w3.org" <public-webapps@w3.org>
Mounir, I ran into the same confusion regarding "how does the API expose
locking?". May I suggest that you explicitly state in the abstract that the
API is pending?

On Wed, Feb 15, 2012 at 8:34 AM, Paul Bakaus <pbakaus@zynga.com> wrote:

> Cool, thanks for the update!
>
> Am 15.02.12 13:21 schrieb "Mounir Lamouri" unter <mounir@lamouri.fr>:
>
> >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
> >
>
>
>
Received on Wednesday, 15 February 2012 18:10:45 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT