[Webkit-unassigned] [Bug 27256] New: Geolocation timeout parameter is not correctly applied

[bugzilla-daemon at webkit.org]

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

           Summary: Geolocation timeout parameter is not correctly applied
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: steveblock at google.com
                CC: andreip at google.com, bolsinga at apple.com


Currently, the Geolocation timeout specified by PositionOptions.timeout is
started only when permissions are granted in Geolocation::setIsAllowed(). This
means that when a call to getCurrentPosition() or watchPosition() is made ...
- If permissions have already been granted, the timeout is not applied
- If permissions have not yet been granted, the timeout is started after a
location has been acquired (and permissions granted).

The intent of the PositionOptions.timeout parameter is to limit the time taken
for the implementation to obtain a location. See
http://www.w3.org/TR/geolocation-API/#position-options. This means that the
timeout should be started as soon as the implementation starts the process of
obtaining the position fix.

Note that the timeout should not include any time taken to obtain permissions
from the user.  It is this fact that allows the parameter to offer
functionality that can not be provided with a JavaScript timer.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.