User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.1b99) Gecko/20090605 Firefox/3.5b99 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.9.1b99) Gecko/20090605 Firefox/3.5b99 (.NET CLR 3.5.30729) I have a LapTop without built-in WiFi. So, I bought a PCMCIA SiteCom Wifi card. I don't use that card at home, only when I travel. When the card is not inserted, and I go to a GeoLocation demo site, it won't work and does not give proper feedback to the user. The browser asks my permission to send the geolocation information. If I confirm, then nothing happens. The browser is still responsive, but as I said, just nothing happens, also no response of failure. I also submitted this bug via Hendrix, but I thought, let I try bugzilla. Reproducible: Always Steps to Reproduce: 1. Buy a computer without WiFi 2. Buy SiteCom WiFi PCMCIA card. 3. Install software for card. 4. Removed card from computer. 5. Go to Geolocation demo site. 6. Give permission. 7. Nothing happens. So, it happens every time that nothing happens. Actual Results: Nothing Expected Results: Geolocation based on IP or proper failure message.
Forget to say, it does work properly when card is inserted.
which site did you go to? Was it the demo page on http://en-us.www.mozilla.com/en-US/firefox/geolocation/ basically trying to determine if it is a single site that has a problem or any/most sites.
I tried your link and the following link: http://channy.creation.net/project/firefox/geolocation.html Both have the same problem, if my card is not inserted. I was not entirely correct about 'nothing happen'. The permission bar on the top of the screen, does disappear. But there is no indication the web-application receives anything. Lucas
Generally GeoIP based location works these days. The geolocation API is a bit cumbersome in that you need to specify a timeout value to ensure that you get back an error callback. Otherwise the browser can take basically forever to try and get a position estimate back to the caller. One idea to improve on this is tracked in the new #1177871.