W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2012

Re: [sensors] Proximity Events

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 23 May 2012 03:24:12 +0200
To: Marcos Caceres <w3c@marcosc.com>
Cc: Doug Turner <dougt@mozilla.com>, "N.V.Balaji" <nv.balaji@samsung.com>, ext Jonas Sicking <jonas@sicking.cc>, public-device-apis@w3.org, Anssi Kostiainen <anssi.kostiainen@nokia.com>, Dzung D ext Tran <dzung.d.tran@intel.com>
Message-ID: <noeor75o4egg8qld7lut08s54tbpphgt71@hive.bjoern.hoehrmann.de>
* Marcos Caceres wrote:
>On 22/05/2012 18:13, Doug Turner wrote:
>>> The reason for the event to bubble is also unclear.
>> These APIs are based on DOM events.  See http://www.w3.org/TR/DOM-Level-2-Events/events.html
>Not sure what you mean, but the event has nothing to "bubble" up to 
>(hence, bubbling has no use case). This also seems to contradict the 
>defaults in DOM4:
>" The bubbles and cancelable attributes must return the values they were 
>initialized to. When an event is created the attributes must be 
>initialized to false."
>Can we just agree to leave it to the DOM4 defaults and not worry about it?

There is no contradiction. The quoted text refers to the value of these
attributes after an event object has been created using `.createEvent`.
Whether any event defined by this Working Group bubbles has do be de-
fined by the Working Group. If the target of the event is the Window
object, it should use the dominant bubbling behavior for events that're
also targeted at the Window object, unless there are good reasons to do
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 23 May 2012 01:24:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:54 UTC