Issue metadata
Sign in to add a comment
|
GeoLocation error callback issue
Reported by
varshu1...@gmail.com,
Nov 15 2017
|
||||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Steps to reproduce the problem:
1. Set the location as "Block Always"
2. Perform any action that tries to access the location
3. Have a timeout for the geolocation.
What is the expected behavior?
the error callback should get called only once. Incase there is "Location error"(Location always blocked) it must execute the error callback. Even if there is a timeout that happens the error callback should not get called .
What went wrong?
The error callback gets called twice . first when there is a location getting error-during location block and the second time during the timeout error.
Here Code A gets called twice. First for location error and next timeout error.
if(navigator.geolocation) {
navigator.geolocation.getCurrentPosition(function(position) {
/*performed var assignment*/ },
function(error) {
if (error.code) {
/*Code A*/
}
},{timeout:2000});
Did this work before? Yes Chrome 61
Does this work in other browsers? Yes
Chrome version: 62.0.3202.89 Channel: n/a
OS Version: OS X 10.12.5
Flash Version:
Happens only during "Always Block" case for a location.
Happens in Chrome62 only.
,
Nov 15 2017
This looks like a duplicate of 784886. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Nov 15 2017