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

PointerLock and Gamepad APIs

From: Darin Fisher <darin@google.com>
Date: Thu, 24 Nov 2011 00:04:19 -0800
Message-ID: <CAP0-QpuR0VHdtLuEjE9z8zAa+0P=5T4AaejzrKF1b=_nkUdz+g@mail.gmail.com>
To: public-webevents@w3.org, Web Applications Working Group WG <public-webapps@w3.org>, Arthur Barstow <art.barstow@nokia.com>
Back in September, it was proposed to expand the charter of the WebEvents
WG to include PointerLock (formerly known as MouseLock) and Gamepad APIs
[1].  This seemed like a logical home for them given that both of these
APIs pertain to input event systems.

However, one thing that became apparent was that Apple was not willing to
join the WebEvents WG [2].  Since we, the Chrome team at Google, work on
WebKit alongside Apple engineers, it is a bit undesirable for us to not be
able to work together with Apple in the WGs, which develop the specs that
we implement in WebKit.  From an efficiency point of view, it is far easier
if we can discuss APIs in a single forum instead of having to relay
concerns between forums.

I'd like to therefore propose that instead of expanding the charter of
WebEvents to include PointerLock and Gamepad, that we instead add those
APIs to another WG such as WebApps.  I believe they make sense in WebApps
given the scope of work being done there and the parties involved.



[2] Recently, Apple disclosed some patents for the Touch Events
specification [
which is currently the only deliverable for the WebEvents WG.
Received on Thursday, 24 November 2011 08:04:48 UTC

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