- From: Vincent Scheib <scheib@google.com>
- Date: Thu, 29 Oct 2015 09:15:24 -0700
- To: "Michael[tm] Smith" <mike@w3.org>
- Cc: Webapps WG <public-webapps@w3.org>
- Message-ID: <CAK-EfX=n0U4dvxOQN1s6S-+szvBzSTJhzApo3v0EUQKMGA8Lbw@mail.gmail.com>
On Thu, Oct 29, 2015 at 12:18 AM, Michael[tm] Smith <mike@w3.org> wrote: > Hi Vincent, > > Vincent Scheib <scheib@google.com>, 2015-10-23 13:57 -0700: > > Testharness tests are not currently able to test the core Pointer Lock > > features, which would require user gesures (mouse clicks) and > synthesizing > > mouse movement. No progress is seen here for this specification, but the > > challenge is present for several. E.g. Web Bluetooth brought up this > > concern recently [Platform Testing] on public-test-infra, but with no > > response. I have requested Jeffrey Yasskin and Sam Uong from Chrome to > > discuss this topic at TPAC. > > To make the needed WebDriver integration into testharness.js happen, the > main thing we have been lacking for more than year or so now is an engineer > committed to spending the weeks of time (say, three months) needed to do > the actual hands-on work of designing it and implementing it and landing > it. > > Hopefully we may finally now be reaching the point where we have critical > mass of people who need to see it happen sooner rather than later. > Good to hear. I should note that for Pointer Lock we would need to carefully spec mouse input at quite a low level, and in a way that will work to fake different OS APIs of mouse change notifications.
Received on Thursday, 29 October 2015 16:16:24 UTC