Closed Bug 1252460 Opened 10 years ago Closed 9 years ago

When you visit http://whatismyipaddress.com/w3c-geolocation the geolocation is not shared

Categories

(Core :: DOM: Geolocation, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox47 --- affected

People

(Reporter: Ovidiu, Unassigned)

References

Details

(Whiteboard: btpp-followup-2016-03-08)

Attachments

(1 file)

Tested on Mac OS X 10.6 with Firefox DeveloperEdition 46.0a2 STR: 1. Go to http://whatismyipaddress.com/w3c-geolocation 2. Select to share location in the doorhanger Expected results: Latitude and Longitude coordinates shall appear. Actual results: Nothing is displayed.
If you look into the preferences in about:config, the value for the geo.wifi.uri preference should be the default: https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY% (that is for nightly/aurora/dev edition). For beta/release the value should be https://www.googleapis.com/geolocation/v1/geolocate?key=%GOOGLE_API_KEY% If the value is correct, can you visit: https://location.services.mozilla.com/v1/geolocate?key=test in the browser? This should return something like: {"fallback": "ipf", "location": {"lat": 53.55, "lng": 10.0}, "accuracy": 25000.0} where the lat/lon fields tell you in which city you are. If this returns an error of some kind, could you post it here?
Hi Hanno, The value is correct in the aurora, I can visit the site that you send it, and yes the browser return me something like you said. I don't see any error.
Ok. So it looks like the underlying geolocation works. Did you try other sites that use geolocation, for example http://html5demos.com/geo to see if it is a site-specific issue?
The whatismyipaddress.com page works correctly with me - an embedded Google Maps appears after a short wait showing my location.
> 1. Go to http://whatismyipaddress.com/w3c-geolocation > 2. Select to share location in the doorhanger > > Expected results: Latitude and Longitude coordinates shall appear. This works for me, too. Doug, you like OS X 10.6 and geolocation, right?
Flags: needinfo?(dougt)
Whiteboard: btpp-followup-2016-03-08
This line may be of interest: https://bugzilla.mozilla.org/show_bug.cgi?id=1252460 On release builds os x core location is not used. Just want to avoid any confusion for someone investigating this, not saying this is related to the cause of this bug. BTW, the rationale behind that ifdef is for MLS data collection, and as part of the GLS-MLS migration, if MLS was used, using core location in release (with the MLS fallback) would provide better geolocation results based on our research.
Works for me in OS X release as well.
Hi, I retested this issue on Mac OS X 10.10 with Nightly 47.0a1 and everything works as expected using this links: http://whatismyipaddress.com/w3c-geolocation http://html5demos.com/geo I run the same test on Mac OS X 10.6, and none of this sites works, nothing is displayed, so I think is related to OS X 10.6. Note: I have also done the test with e10s enabled and disabled, and the results is the same, so is not a e10s related issue.
I also try this scenario on Mac OS X 10.6 with FF DeveloperEdition: 1. Go to https://www.google.ro/maps?source=tldso 2. Click the "Show my location" button from Google Maps controls 3. From the doorhanger select "Share Location" Expected results: The user location is highlighted on Google Maps Actual Results: after 10 sec. I receive a message: "You location couldn't be identified"
WFM in version 44.0.2. In about:config, can you search for "geo." and tell us the values of the preferences listed?
Flags: needinfo?(dougt)
Hi, This is what I found in "geo" from about:config geo.enabled - true geo.provider.use_corelocation - true geo.wifi.uri - https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY% geo.wifi.xhr.timeout - 60000
Could you try to change the geo.provider.use_corelocation property to false, restart the browser and try again? This might be a bad interaction between core location and OS X 10.6.
Hi Hanno, I changed the geo.provider.use_corelocation property to false and the problem was solved.
(In reply to ovidiu boca[:Ovidiu] from comment #14) Hi Ovidio, would you please check the console (from the Developer Tools) for error messages?
Hi, I attached a file with the browser console output.
Ovidio, thanks for that. Would you please do the following on your 10.6 machine? 1. Double-check that CoreLocation is enabled correctly in your System Preferences (Privacy?) 2. Using a recent Nightly, be sure that the preference geo.provider.use_corelocation is set to TRUE 3. Restart the Nightly 3. Go to Google Maps or some other service to check if the location gets correctly provided? If this leads to another failure we might think to just disable CoreLocation altogether on 10.6 and just rely on MLS/GLS to be sure everything works.
Flags: needinfo?(ovidiu.boca)
Hi Michelangelo, I checked if CoreLocation is enabled on my System Preferences. I used the latest FF Nightly 50.0a1 (2016-07-04), I set the pref and I restart the browser. The issue is still there.
Flags: needinfo?(ovidiu.boca)
Also I know that support for version older than Mac 10.8 will be dropped out soon.
(In reply to ovidiu boca[:Ovidiu] from comment #19) > Also I know that support for version older than Mac 10.8 will be dropped out > soon. :Ovidiu, thanks for filing this and following up so promptly. Firefox 51 has shipped few days ago and we're not supporting versions of macOS earlier than 10.9 [1]. I'm gonna mark this as WFM and I hope you'll be keeping you eyes open for more regressions with Geolocation (not too many I hope!:)). [1] https://www.mozilla.org/en-US/firefox/51.0.1/system-requirements/
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: