79858 2012-02-28 19:11:05 -0800 The way we invalidate high accuracy geolocation listener is incorrect 2012-05-21 12:08:47 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 41341 InRadar P2 Normal --- 1 benjamin benjamin ap steveblock oldest_to_newest 567326 0 benjamin 2012-02-28 19:11:05 -0800 Add a high accuracy Add a non-high accuracy Remove the high accuracy -->we stay in high accuracy The problem is we have one client for all the controller, and the controller assume its client manage setEnableHighAccuracy per controller: void GeolocationController::removeObserver(Geolocation* observer) { if (!m_observers.contains(observer)) return; m_observers.remove(observer); m_highAccuracyObservers.remove(observer); if (m_client) { if (m_observers.isEmpty()) m_client->stopUpdating(); else if (m_highAccuracyObservers.isEmpty()) m_client->setEnableHighAccuracy(false); } } 567795 1 benjamin 2012-02-29 11:50:36 -0800 <rdar://problem/10951749> 629227 2 steveblock 2012-05-21 10:13:59 -0700 > The problem is we have one client for all the controller, and the controller > assume its client manage setEnableHighAccuracy per controller: Do you mean that you're sharing a single implementation of GeolocationClient between all GeolocationController instances? That would be a port-specific bug. Is this on Mac? 629235 3 steveblock 2012-05-21 10:24:03 -0700 Having re-read this bug, I think you're referring to the problem in Bug 41341 ? 629355 4 benjamin 2012-05-21 12:08:47 -0700 Yep. I close this bug as duplicate. *** This bug has been marked as a duplicate of bug 41341 ***