Re: [battery] Battery testing and implementation report update

Hi Frederick, Zhiqiang,

> On 06 Feb 2015, at 18:10, 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

Chromium implementation per the latest CR is shipping, while the Firefox implementation is being revised to match the latest CR (Firefox implements an earlier versions of the spec, pre-promises).

I updated the wiki accordingly.

> If this is the case the following additional steps are needed:
> 
> 1. Run the tests on the Chromium implementations

Correct, but only after ACTION-730 has been addressed (as you noted in your response):

https://www.w3.org/2009/dap/track/actions/730

> 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?

Zhiqiang is probably able to estimate how big an effort it'd be to update the test suite to match the latest spec (and will also welcome PRs :-)). I sent some suggestions for tasks at:

https://lists.w3.org/Archives/Public/public-device-apis/2015Feb/0005.html

Someone from Mozilla's side may be able to give us a guesstimate for updating the implementation. I think the person to whom the implementation is assigned to is not in this WG.

After the test suite is revised and Mozilla has updated its implementation, we can consider progressing to PR.

Thanks,

-Anssi

Received on Monday, 9 February 2015 11:59:14 UTC