<plh> https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-battery-status-20111129/doc/

<plh> http://lists.w3.org/Archives/Public/public-device-apis/2012Jan/0020.html

<plh> that's for https://www.w3.org/2006/02/lc-comments-tracker/43696/WD-battery-status-20111129/2574

PLH asks about the last call comment to Anne, but the link seems to be to something else

The connection to the last call tracker database is currently down :(

Anssi: we addressed Anne's comments and he says it is fine.

<plh> http://lists.w3.org/Archives/Public/public-device-apis/2011Dec/0005.html

Anssi: this is essentially an editorial comment and has been handled as you can see (explains).

Frederick: I updated the tracker to note that the comments were all addressed.

PLH: a little bit startled by the comment in the security and privacy considerations section.

Anssi notes that we added this section following feedback from Mozilla.

PLH: are there any optional features in the battery spec?

Anssi: no, we avoided that through our design, and with implementation feedback from Mozilla.

PLH: implementations?

Anssi: we have at least two implementations currently, e.g. one in several flavors of Mozilla, the other is webkit.

PLH: any others?

Anssi: this would be Microsoft or Opera Software

<fjh> http://www.w3.org/2009/dap/wiki/ImplementationStatus#Battery_Status_API

PLH: Chrome?

<AnssiK> navigator.webkitBattery

<AnssiK> BatteryManager

<AnssiK> . charging: true

<AnssiK> . chargingTime: Infinity

<AnssiK> . dischargingTime: Infinity

<AnssiK> . level: 1

Anssi: yes, chrome appears to have an implementation.

<AnssiK> . onchargingchange: null

<AnssiK> . onchargingtimechange: null

<AnssiK> . ondischargingtimechange: null

<AnssiK> . onlevelchange: null

<AnssiK> . __proto__: BatteryManager

Anssi: so we have 3 webkit ports supporting battery status.

PLH: what about tests?

Anssi: we have some work on that to do

PLH: I have no problem with battery moving to CR, congrats

<AnssiK> great, thanks!

PLH: next the vibration spec, looks good, any optional features?

Anssi: no, it is a very simple spec.

PLH: implementations?

Anssi: Firefox and Blackberry webkit port, so at least 2 implementations and depending on how you count it maybe 3

Chrome doesn't seem to support it yet, but I am aware of a couple of other ports in progress.

PLH: no further questions, so I am happy for vibration to move to CR.

What about test suites for vibration?

Anssi: we need to do a little more work, although we have a skeleton test suite, so it is off to a good start.

The design prevents background pages activating the vibration device.

<AnssiK> thanks plh, all!

<fjh> Thank you.

<plh> welcome

PLH: thanks and congrats on both specs moving to CR!

<scribe> scribe: dsr

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/changed this/added this section/
Found Scribe: dsr
Inferring ScribeNick: dsr

WARNING: No "Topic:" lines found.

Present: PLF fjh AnssiK dsr
Got date from IRC log name: 27 Apr 2012
Guessing minutes URL: http://www.w3.org/2012/04/27-dap-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report