144626 2015-05-05 06:18:32 -0700 Determining current location takes too long 2025-11-04 22:18:10 -0800 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Unspecified OS X 10.10 RESOLVED WORKSFORME InRadar P2 Normal --- 1 julienq webkit-unassigned marcosc webkit-bug-importer oldest_to_newest 1091741 0 252378 julienq 2015-05-05 06:18:32 -0700 Created attachment 252378 A test that shows the current location and how long it took to acquire in the console Using the Geolocation API to determine user location (either using getCurrentLocation or watchPosition) takes too long in WebKit (around 5 to 10 seconds, sometimes more than that) compared to other browsers (e.g. Chrome takes either around 200ms or around 2s) on the same OS, Wifi network, location, &c. Strangely, when launching WebKit or Safari, user location can be extremely quick (just a few dozen milliseconds at most) and then after several uses it becomes slow. 1091742 1 webkit-bug-importer 2015-05-05 06:18:52 -0700 <rdar://problem/20816885> 2156510 2 marcosc 2025-11-04 22:18:10 -0800 Closing as works for me, as I'm seeing 400ms response times. 252378 2015-05-05 06:18:32 -0700 2015-05-05 06:18:32 -0700 A test that shows the current location and how long it took to acquire in the console geolocation.html text/html 262 julienq PHNjcmlwdD4KdmFyIHQgPSBEYXRlLm5vdygpOwp3aW5kb3cubmF2aWdhdG9yLmdlb2xvY2F0aW9u LmdldEN1cnJlbnRQb3NpdGlvbihmdW5jdGlvbihwb3NpdGlvbikgewogICAgY29uc29sZS5sb2co IkdvdCBwb3NpdGlvbjoiLCBwb3NpdGlvbiwgRGF0ZS5ub3coKSAtIHQpOwp9LCBmdW5jdGlvbihl cnJvcikgewogICAgY29uc29sZS5lcnJvcigiRXJyb3IgZ2V0dGluZyBwb3NpdGlvbjoiLCBlcnJv ciwgRGF0ZS5ub3coKSAtIHQpOwp9KTsKPC9zY3JpcHQ+Cg==