51814 2011-01-03 03:25:14 -0800 GeolocationPositionCache should not start background thread until a Geolocation method is called 2011-07-29 06:08:32 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) All All RESOLVED INVALID P2 Normal --- 51818 1 steveblock webkit-unassigned jorlow steveblock oldest_to_newest 328507 0 steveblock 2011-01-03 03:25:14 -0800 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. 330146 1 jorlow 2011-01-06 08:02:02 -0800 >> 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. 443910 2 steveblock 2011-07-29 06:08:32 -0700 GeolocationPositionCache was removed in Bug 65289