RESOLVED INVALID Bug 51814
GeolocationPositionCache should not start background thread until a Geolocation method is called 
https://bugs.webkit.org/show_bug.cgi?id=51814
Summary GeolocationPositionCache should not start background thread until a Geolocati...
Steve Block
Reported 2011-01-03 03:25:14 PST
Currently, we start the DB thread as soon as navigator.geolocation is accessed. Then when a Geolocation method is called, we potentially use a cached position if one is available, but we don't wait for the cache. We should change this to avoid starting up the background thread when navigator.geolocation is accessed, but its methods are not called.
Attachments
Add attachment proposed patch, testcase, etc.
Jeremy Orlow
Comment 1 2011-01-06 08:02:02 PST
>> This >> seems silly since people often fetch the geolocation object in feature >> detection, even if they are not using it. > > Really, do you think it's likely that people feature detect for a feature they don't plan to use? Yes, libraries do this all the time. I should have caught this in the original review. Please prioritize fixing this.
Steve Block
Comment 2 2011-07-29 06:08:32 PDT
GeolocationPositionCache was removed in Bug 65289
Note You need to log in before you can comment on or make changes to this bug.