- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Fri, 5 Sep 2014 07:02:17 +0000
- To: "Zhang, Zhiqiang" <zhiqiang.zhang@intel.com>, Frederick Hirsch <w3c@fjhirsch.com>, W3C Device APIs WG <public-device-apis@w3.org>
On 05 Sep 2014, at 09:38, Zhang, Zhiqiang <zhiqiang.zhang@intel.com> wrote: > I just updated vibration implementation report at > > http://w3c.github.io/test-results/vibration/all.html > > ... with testing results for both Android mobile and Windows desktop, with the fact that mobile has a vibrator while desktop hasn't. > >> From the report we can see that > > - All tests pass on Chrome 35 for Android and Firefox 33 Nightly for Android (mobile). > - API tests pass on Chrome 39 for Windows and Firefox 35 Nightly for Windows (desktop); but manual tests get no vibration as desktop has no vibrator, so fail. This is expected. > > As usual, updated the wiki page too > > https://www.w3.org/2009/dap/wiki/ImplementationStatus Looks good to me, this should address the issue. The table on the ImplementationStatus wiki also explains (as above) that the failure is expected on devices with no vibrator. I guess this report now satisfies the CR exit criteria. Frederick - please let us know if something is still missing considering the CR exit. Do we need to create a stable snapshot of this report at the time we move to PR, or is this fine? Thanks, -Anssi
Received on Friday, 5 September 2014 07:03:09 UTC