- From: Anne van Kesteren <annevk@opera.com>
- Date: Tue, 06 Sep 2011 14:04:06 +0200
- To: www-dom@w3.org, "Robin Berjon" <robin@berjon.com>
- Cc: public-device-apis@w3.org
On Tue, 06 Sep 2011 13:57:26 +0200, Robin Berjon <robin@berjon.com> wrote: > The battery event is defined in such a way that it is neither > cancellable nor bubbling. However, in line with other init*Event > methods, options are provided to define synthetic such events as > cancellable or bubbling. The question is therefore: what's the right > thing to do when either are set to true? > > a) Synthesise an event that bubbles and can be cancelled? > b) Ignore those and synthesise an event that doesn't? > b') If (b), should we remove them from the signature? > > Thanks in advance for your keen insights! The answer is a). Synthetic events should have no effect whatsoever and can be whatever they want. > [0] http://dev.w3.org/2009/dap/system-info/battery-status.html -- Anne van Kesteren http://annevankesteren.nl/
Received on Tuesday, 6 September 2011 12:04:38 UTC