- From: Andrei Popescu <andreip@google.com>
- Date: Wed, 13 Jul 2011 15:23:34 +0100
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Wojciech Maslowski <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. Thanks, Andrei
Received on Wednesday, 13 July 2011 14:24:10 UTC