Bug 144626

Summary:

Determining current location takes too long

Product:

WebKit

Reporter:

Julien Quint <julienq>

Component:

New Bugs

Assignee:

Nobody <webkit-unassigned>

Status:

RESOLVED WORKSFORME

Severity:

Normal

CC:

marcosc, webkit-bug-importer

Priority:

Keywords:

InRadar

Version:

528+ (Nightly build)

Hardware:

Unspecified

OS:

OS X 10.10

Attachments:

Description	Flags
A test that shows the current location and how long it took to acquire in the console	none

Julien Quint

Reported 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.

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 attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2015-05-05 06:18:52 PDT

<rdar://problem/20816885>

Marcos Caceres

Comment 2 2025-11-04 22:18:10 PST

Closing as works for me, as I'm seeing 400ms response times.

Note You need to log in before you can comment on or make changes to this bug.