Bug 144626 - Determining current location takes too long
Summary: Determining current location takes too long
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified OS X 10.10
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-05-05 06:18 PDT by Julien Quint
Modified: 2015-05-05 06:18 PDT (History)
1 user (show)

See Also:

Attachments
A test that shows the current location and how long it took to acquire in the console (262 bytes, text/html)
2015-05-05 06:18 PDT, Julien Quint 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Quint 2015-05-05 06:18:32 PDT 
Created attachment 252378 [details]
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.
Comment 1 Radar WebKit Bug Importer 2015-05-05 06:18:52 PDT 
<rdar://problem/20816885>