I should note that I do have an application in the oven that could serve as a usecase study for non fullscreen pointerlock UX/issues (it uses pointerlock in different portions of its functionality to improve usability). It's currently not ready for release, but upon request I can arrange for a personal preview, and I plan to make a first release soon. On Fri, Jan 4, 2013 at 7:04 PM, Vincent Scheib <scheib@google.com> wrote: > On Fri, Jan 4, 2013 at 4:49 AM, Arthur Barstow <art.barstow@nokia.com>wrote: > >> Hi Vincent, >> >> Seeing this discussion, and noting two open [Bugz], I was wondering about >> the plan to get this spec to a feature complete status (and hence ready for >> Last Call Working Draft). Would you please provide a short status/plan for >> Pointer Lock spec vis-ā-vis LCWD? >> >> -Thanks, AB >> >> [Bugz] <https://www.w3.org/Bugs/**Public/buglist.cgi?product=** >> WebAppsWG&component=Pointer%**20Lock&resolution=---&list_id=**3760<https://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&component=Pointer%20Lock&resolution=---&list_id=3760> >> > > > > The discussion about how easily javascript shims can be created is > orthogonal to the pointer lock spec. I'll leave that discussion on that > thread, which I note has concluded in "pointer lock has apparently already > been shimmed". > > Of the two open issues, one [1] was already resolved (adding > allow-pointer-lock to HTML). I've closed the issue. > > The other [2] is blocked on Mozilla's security review [3]. > > [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=18647 > [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=19297 > [3] https://bugzilla.mozilla.org/show_bug.cgi?id=822654 > >
Received on Friday, 4 January 2013 18:42:06 UTC