- From: Frederick Hirsch <w3c@fjhirsch.com>
- Date: Fri, 6 Feb 2015 11:18:55 -0500
- To: "Zhang, Zhiqiang" <zhiqiang.zhang@intel.com>, Marcos Caceres <w3c@marcosc.com>
- Cc: W3C Device APIs WG <public-device-apis@w3.org>, Dominique Hazael-Massieux <dom@w3.org>
as a reminder, we also have an open action to update the Battery Status API test suite to conform to the specification, thus the updated tests will also have to be run on Firefox action: https://www.w3.org/2009/dap/track/actions/730 (apologies I missed noting this in the original email) regards, frederick On Feb 6, 2015, at 11:10 AM, Frederick Hirsch <w3c@fjhirsch.com> wrote: > Currently the Battery Status API implementation report shows only one implementation (Firefox) for the Battery Status API: > > http://www.w3.org/2009/dap/wiki/ImplementationStatus > > It looks like Chromium has both a desktop and Android implementation for Chromium 38, or am I mistaken? > > https://www.chromestatus.com/features/4537134732017664 > > If this is the case the following additional steps are needed: > > 1. Run the tests on the Chromium implementations > > 2. Create an implementation report document, similar to what we have for the Vibration API, http://w3c.github.io/test-results/vibration/20141118.html > > Once we have an updated implementation report I think we can consider progressing the Battery Status API to PR. > > Are you able to work on this and do you have an estimate of how long it might take? > > Thanks > > regards, Frederick > > Frederick Hirsch > Chair W3C Device APIs WG (DAP) > > http://www.fjhirsch.com/ > w3c @ fjhirsch.com ; @fjhirsch > > >
Received on Friday, 6 February 2015 16:19:31 UTC