I would like to drop webkit prefix from Battery Status API. - Battery Status API have been changed CR. - Mozilla implemented Battery Status API to the Gecko and the Firefox enabled this API already.
Created attachment 155765 [details] Patch
This API is more substantial than the vibrate API, so having a test suite makes more sense. Is there a test suite that we and Firefox pass?
(In reply to comment #2) > This API is more substantial than the vibrate API, so having a test suite makes more sense. Is there a test suite that we and Firefox pass? I made a test case. http://hackerslab.eu/test/batterystatus.html We can see the same result between Firefox and Efl test browser. Thank you.
Per Anssi (who I've cc'ed): there is an action item for writing a test-suite for the Battery Status and Vibration APIs. Kihong, do you think we should wait for that -maybe contribute our tests to it?- to verify the implementation prior to unprefixing? https://www.w3.org/2009/dap/track/actions/523 For reference, bug 92964 came up today, which was an incompatibility that should have been caught by some test.
Comment on attachment 155765 [details] Patch I agree. When battery test cases is opened, I will raise this issue after testing.
I started working on a test suite for the Battery Status API: http://w3c-test.org/dap/battery/tests/submissions/anssik/ It is work in progress, I'll let you know when the test coverage improves. Do you have re-usable test assets? I'm using testharness.js as the test framework.
We removed this API in https://trac.webkit.org/changeset/208300