W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2015

Re: [pointerlock] Oct 2015 Pointer Lock Status

From: Florian Bösch <pyalot@gmail.com>
Date: Mon, 2 Nov 2015 04:15:28 +0100
Message-ID: <CAOK8ODgxYFV6C-9Rx7cjekUzUFiJBZDg1U+hvg5rpnmZBhhkmQ@mail.gmail.com>
To: Vincent Scheib <scheib@google.com>
Cc: Chaals McCathie Nevile <chaals@yandex-team.ru>, Webapps WG <public-webapps@w3.org>
On Sun, Nov 1, 2015 at 9:08 PM, Vincent Scheib <scheib@google.com> wrote:
>
> Thanks for clarifying. Basic usage is demonstrated in the wild but some
> edge cases should have clear demonstration in the test suite. I will
> generate those as other project priorities allow (and would of course
> review any from others).
>

One of the things that frequently go wrong with pointerlock in the wild is
that authors request it, but don't check the result of the authorization.
They then go on to write applications that only work right with pointerlock
(for example FPS controls), and UAs deny pointerlock (because the user
needs to click an allow button). The dialog to allow pointerlock is not
modal and it's also presented small at the top of the screen, so it's
frequently missed.
Received on Monday, 2 November 2015 03:15:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:58 UTC