- From: Taqi Jaffri <tjaffri@microsoft.com>
- Date: Tue, 31 Mar 2009 11:14:17 -0700
- To: Doug Turner <doug.turner@gmail.com>, Andrei Popescu <andreip@google.com>
- CC: public-geolocation <public-geolocation@w3.org>
+1. This is something we have also discussed internally, and it makes a lot of sense. -----Original Message----- From: public-geolocation-request@w3.org [mailto:public-geolocation-request@w3.org] On Behalf Of Doug Turner Sent: Tuesday, March 31, 2009 11:00 AM To: Andrei Popescu Cc: public-geolocation Subject: Re: renaming enableHighAccuracy +1 On Mar 31, 2009, at 10:53 AM, Andrei Popescu wrote: > Hi, > > The 'enableHighAccuracy' attribute continues to generate a lot of > controversy so I'd like to propose renaming it. > > The main reason why it exists is to allow Web developers to say that > their application works fine with low-accuracy position fixes and, > therefore, the UA should not bother turning on location providers that > consume a lot of power. Web developers care about power consumption > since, on mobile devices especially, this has an impact on how long > their applications can be used. So how about renaming this attribute > to "lowPowerOnly" (thanks to Steve Block for the suggestion) ? This > name is closer to the intended effect: a hint that the implementation > should make use of only what it considers to be low power providers. > What is a low power provider is left to the implementation to decide, > but a reasonable course of action would be to avoid powering up the > GPS when "lowPowerOnly" attribute is set to true. > > Thanks, > Andrei >
Received on Tuesday, 31 March 2009 18:15:05 UTC