545093 - No result of geo location when using document.open many times.

Status: RESOLVED DUPLICATE of bug 596481

(Core :: DOM: Geolocation, defect)

Description

[Christian Seifert]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)

Developing an application using AJAX requests to replace the current page via document.open, I make use of the geo location feature. But unfortunataly after some document replacements the geo location function "getCurrentPosition" doesn't work as expected any more. Both callbacks aren't fired and it seems that the function simply doesn't response.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.treibeisen.de/geo.html which is a test
2. Accept the awareness about geo location access
3. Click several times on "Reload via document.open"

After some clicks the geo coords should simply disappear instead of calling the success or fail callback.
Actual Results:  
The getCurrentPosition's callbacks aren't called every time.

Expected Results:  
Calling the callback functions any time after invoking getCurrentPosition and delivering the geo coords, of course.

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a2pre) Gecko/20100208 Minefield/3.7a2pre

I see the problem indeed with Firefox 3.5, but it seems fixed (more or less) with latest 3.6 and trunk.
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.2/
After 20+ reloads however the bug shows up again. So improved but not entirely fixed.

Comment 2

[George Lee]

I see this same bug in my browser as well:

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

After repeated geolocations, getCurrentPosition's callbacks stop getting called. At that point, reloading the page does not fix the problem, but restarting firefox does fix the problem.

Using wireshark, I can see that the wifi data is sent to Google and a response is coming back from google quickly, but getCurrentPosition's callbacks are not called.

Comment 3

[Tom Wuttke]

This is a dup of 596481, which is now understood to be caused by positions getting cached globally and less accurate positons being rejected, preventing any callbacks from firing until the entire browser is restarted. 

I don't know how to mark a bug as a dup.