- From: Michael van Ouwerkerk <mvanouwerkerk@google.com>
- Date: Mon, 14 Jul 2014 11:38:42 +0100
- To: "Zhang, Zhiqiang" <zhiqiang.zhang@intel.com>
- Cc: W3C Device APIs WG <public-device-apis@w3.org>
- Message-ID: <CAF40kP45UuN9tFV5DM4e3HegfPJmNbScmEqZOSq48jR=k8dTYw@mail.gmail.com>
Thanks Zhang! On Mon, Jul 14, 2014 at 8:19 AM, Zhang, Zhiqiang <zhiqiang.zhang@intel.com> wrote: > > From: Zhang, Zhiqiang [mailto:zhiqiang.zhang@intel.com] > > Sent: Friday, June 27, 2014 5:30 PM > > > From: Frederick Hirsch [mailto:w3c@fjhirsch.com] > > > Sent: Thursday, June 26, 2014 9:06 PM > > > For vibration I notice there is one 'fail' for Firefox. What do we > have to do > > to > > > address this 'fail' - is there an action on someone? I assume once > this fail is > > > addressed then we are done testing Vibration, have two implementations > > > and could progress toward Recommendation. > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1031226 reported for > Firefox > > for Android. > > This issue is fixed and verified on Firefox for Android Nightly. So we've > gotten all tests pass on both Chrome 35 and Firefox 33. Please check the > update test results at > > https://www.w3.org/2009/dap/wiki/ImplementationStatus > > Revisiting @darobin's TODO list at > > https://github.com/w3c/web-platform-tests/blob/master/vibration/TODO.txt > > ... we still miss tests for > > - do nothing when hidden > - cancel when dynamically hidden > - reinstate when dynamically shown > Reinstatement should not happen: "When the visibilitychange event [PAGE-VISIBILITY] is dispatched at the Document in a browsing context, the user agent must cancel the pre-existing instance of the processing vibration patterns algorithm, if any." It is canceled, not suspended. Regards, Michael > - invalid values > > If you have tests for these checkpoints or want to write some, feel free > to submit them to > > https://github.com/w3c/web-platform-tests/tree/master/vibration > > Thanks, > Zhiqiang > >
Received on Monday, 14 July 2014 10:39:09 UTC