W3C home > Mailing lists > Public > public-secondscreen@w3.org > March 2015

onavailablechange event target

From: Oleg Beletski <o.beletski@samsung.com>
Date: Wed, 25 Mar 2015 11:36:50 +0000
To: "public-secondscreen@w3.org" <public-secondscreen@w3.org>
Message-id: <E36445936A572743840F0BF1A5EC5FED4CD12105@ex1.seri.co.uk>

In Presentation API specification the NavigatorPresentation interface is an EventTarget and is an attribute of the Navigator.

We have noticed that other APIs that provide some data about global state of the Navigator do not use it as an event target because of some reasons. Examples are online/offline events and Gamepad API. There is the navigator.onLine property but events (online, offline) are both dispatched on the Window object. Gamepad API designed in a similar way. Gamepad interface has a attribute "connected" but then events (gamepadconnected, gamepaddisconnected) are fired against the window.

What could be the reason why existing APIs do not use Navigator properties an EventTarget and what the correct way to do that?

Then we also noticed some typos in the working draft in section 7.4 and 8. that mention that events is fired against the PresentationSession (should be the NavigatorPresentation with current design).

Best regards,
Oleg Beletski
Principal Engineer
Samsung Electronics R&D, Finland, Espoo
Received on Wednesday, 25 March 2015 11:37:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:51 UTC