Re: [battery] Alternative design proposal (was: addEventListener side effects, ordering & boundary crossing ...) from Dominique Hazael-Massieux on 2011-09-07 (public-device-apis@w3.org from September 2011)

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Wed, 07 Sep 2011 16:10:57 +0200
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Cc: "public-device-apis@w3.org WG" <public-device-apis@w3.org>, ext Anne van Kesteren <annevk@opera.com>
Message-ID: <1315404664.5921.464.camel@altostratustier>

Le mercredi 07 septembre 2011 à 14:27 +0300, Anssi Kostiainen a écrit :
> Given the recent insightful discussion on public-device-apis and www-dom mailing lists, I decided to migrate the alternative proposal from its strawman form into an Editor's Draft for better readability:
>   http://dev.w3.org/2009/dap/system-info/battery-status.html
> To refer to the previous Editor's Draft, see:

I like the new approach; I wonder whether we need to allow the creation
of new batterystatuseventsource, vs defining window.navigator.battery as
the well-known instance of that interface.

Dom

Received on Wednesday, 7 September 2011 14:11:14 UTC