W3C home > Mailing lists > Public > public-geolocation@w3.org > July 2011

Re: Spec update: deviceorientation event should fire when listener is first registered

From: Andrei Popescu <andreip@google.com>
Date: Wed, 13 Jul 2011 15:23:34 +0100
Message-ID: <CAGn1-_UOAY9wpXMnXGgOPi9TD8f=JkXB1mKaVM9U3ZZwnqYrgg@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: (wrong string) Å‚owski <wmaslowski@opera.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, public-geolocation <public-geolocation@w3.org>
On Wed, Jul 13, 2011 at 2:55 PM, Anne van Kesteren <annevk@opera.com> wrote:
> On Wed, 13 Jul 2011 15:38:18 +0200, Anne van Kesteren <annevk@opera.com>
> wrote:
>> I do not really see how it contradicts it. Setting the attribute does that
>> *and* causes an event to be dispatched (or starts some process in the case
>> of MessagePort). The pattern was discussed a while back on the WHATWG list.
> By the way I am not saying you should use this pattern. Maybe as Björn
> indicated you need another approach to this API. Have the information
> hanging off from the Navigator object somewhere and dispatch an event using
> the basic Event interface when the information has changed.

Yep, we should discuss that. The basic issue there is that we'd have
to keep the information fresh on this object, which means always
exercising the underlying hardware, even if no page is using it.

Received on Wednesday, 13 July 2011 14:24:10 UTC

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