[Webkit-unassigned] [Bug 144626] New: Determining current location takes too long

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=144626

            Bug ID: 144626
           Summary: Determining current location takes too long
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Mac OS X 10.10
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: julienq at apple.com
                CC: webkit-bug-importer at group.apple.com

Created attachment 252378
  --> https://bugs.webkit.org/attachment.cgi?id=252378&action=review
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150505/1a109e17/attachment.html>