这个库为地理定位调用添加了一个desiredAccuracy和maxWait选项，这意味着它将继续尝试获取位置，直到精度在指定的范围内。

这对我来说每次都管用:

navigator.geolocation.getCurrentPosition(getCoor, errorCoor, {maximumAge:60000, timeout:5000, enableHighAccuracy:true});

虽然它不是很准确。有趣的是，在同一台设备上，如果我运行这个程序，它会把我拖走大约100米(每次)，但如果我去谷歌的地图，它会准确地找到我的位置。因此，尽管我认为enableHighAccuracy: true有助于它始终如一地工作，但它似乎并没有使它更准确……

我也遇到了同样的情况。我尝试了超时解决方案，但不可靠。我发现如果你只调用它两次，位置就会正确刷新

function getLocation(callback)
{   
    if(navigator.geolocation)
    {
        navigator.geolocation.getCurrentPosition(function(position)
        {
            navigator.geolocation.getCurrentPosition(callback, function(){},{maximumAge:0, timeout:10000});
        },function(){}, {maximumAge:0, timeout:10000});
    }
    return true;
}

这当然是有点慢，但我没有给我错误的位置一次。我有它击中超时几次，没有返回任何东西，但除此之外，它工作得很好。我知道这仍然有点老套，我期待有人找到真正的解决方案。

或者，如果你想确保它会一直尝试，直到你想放弃，你可以试试这样的方法。

//example
$(document).ready(function(){
    getLocation(function(position){
        //do something cool with position
        console.log(position);
    });
});


var GPSTimeout = 10; //init global var NOTE: I noticed that 10 gives me the quickest result but play around with this number to your own liking


//function to be called where you want the location with the callback(position)
function getLocation(callback)
{   
    if(navigator.geolocation)
    {
        var clickedTime = (new Date()).getTime(); //get the current time
        GPSTimeout = 10; //reset the timeout just in case you call it more then once
        ensurePosition(callback, clickedTime); //call recursive function to get position
    }
    return true;
}

//recursive position function
function ensurePosition(callback, timestamp)
{
    if(GPSTimeout < 6000)//set at what point you want to just give up
    {
        //call the geolocation function
        navigator.geolocation.getCurrentPosition(
            function(position) //on success
        {
                //if the timestamp that is returned minus the time that was set when called is greater then 0 the position is up to date
            if(position.timestamp - timestamp >= 0)
                {
                    GPSTimeout = 10; //reset timeout just in case
                    callback(position); //call the callback function you created
                }
                else //the gps that was returned is not current and needs to be refreshed
                {
                    GPSTimeout += GPSTimeout; //increase the timeout by itself n*2
                    ensurePosition(callback, timestamp); //call itself to refresh
                }
            },
            function() //error: gps failed so we will try again
            {
                GPSTimeout += GPSTimeout; //increase the timeout by itself n*2
                ensurePosition(callback, timestamp);//call itself to try again
            },
            {maximumAge:0, timeout:GPSTimeout}
        )
    }       
}

我可能在这里有一些打字和拼写错误，但我希望你能明白。如果有人有问题或者找到更好的建议，请告诉我。

我在使用Firefox的响应式设计模式时就遇到过这种情况。已经提交了一份错误报告。现在，在使用地理定位API时不要使用响应式设计模式。

截至2020年年中，这里的答案都没有提供任何解释，只是黑客攻击或猜测。

正如@Coderer在我之前指出的，安全上下文(https)是今天需要的，所以在越来越多的设备上，地理定位在普通http下根本不起作用:

安全上下文 此特性仅在安全上下文中(HTTPS)以及部分或所有支持的浏览器中可用。

getCurrentPosition()(和watchPosition()更适合这里)的第三个参数是PositionOptions对象，由以下属性组成:

enableHighAccurancy (default false): if set to true, response is slower and more accurate. If you got timeout errors, keep this to false. If the accurancy is low, set it to true. In my tests the accurancy varies and on some devices it has no effect. On other devices setting true may cause surprisingly quick battery depletion. timeout (default infinity): milliseconds before the API gives up and calls the error handler (the second parameter). Today most mobile devices with geolocation enabled and permission granted for the browser/page get the value with reasonable accurancy within a second. When the geolocation service is not available, alternative method like geo IP may be used, the delay can be many seconds and the precision usually ranges from questionable to useless. maximumAge (default 0): milliseconds when cached value is valid, the device may decide to use valid cached data instead of sensor measure. I usually set this to non-zero values with slowly moving devices (like walking with mobile phone). On static devices, Infinity can be set to avoid consequent reading errors.

正如@YoLoCo在我之前指出的那样，getCurrentPosition()和watchPosition()会干扰，我在2020年确认了他的结果。通常，使用watchPosition代替getCurrentPosition周期性调用。

我最近自己也注意到了这个问题，我不确定它是怎么来的，但它有时会出现firefox在缓存中加载的东西上卡住。在清除缓存并重新启动firefox后，它似乎再次发挥作用。