| Summary: | Determining current location takes too long | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Julien Quint <julienq> | ||||
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | OS X 10.10 | ||||||
| Attachments: |
|
||||||
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.