Bug 233095 - www/firefox geolocation no longer working
Summary: www/firefox geolocation no longer working
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-gecko mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-09 20:59 UTC by J.R. Oldroyd
Modified: 2018-12-19 17:54 UTC (History)
2 users (show)

See Also:
jbeich: maintainer-feedback? (chromium)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description J.R. Oldroyd 2018-11-09 20:59:37 UTC
The geolocation code in netwerk/wifi/nsWifiScannerFreeBSD.cpp is failing to return lat/lon location.

Repeat by going to:
    http://html5demos.com/geo
Grant it location access permission.  It fails.  It should work and show your lat/lon position.

I wrote the code in nsWifiScannerFreeBSD.cpp back in 2012.  I believe the wifi lookup code itself is still good.  I have verified it is being compiled in (it is, it's in libxul.so).  I have run firefox with debugging enabled and see that the code is still finding the local wifi networks (run firefox with "-MOZ_LOG=timestamp,WifiMonitor:4" to see this).

A manual test of the geolocation API per the instructions here:
    https://developers.google.com/maps/documentation/geolocation/intro
seems to show that the API key we are using has expired and billing needs to be enabled on it.  Firefox appears to be getting the daily usage limit exceeded error.
Comment 1 Jan Beich freebsd_committer 2018-11-10 00:23:49 UTC
Does geolocation work in www/chromium? That's where the API key originates. Like with SafeBrowsing the quota has to be extended. Unfortunately, I don't know who to contact.
Comment 2 J.R. Oldroyd 2018-11-10 13:06:17 UTC
Just tried it.  No, it fails on www/chromium too.
Comment 3 J.R. Oldroyd 2018-12-19 17:54:22 UTC
According to this page:
    http://www.chromium.org/developers/how-tos/api-keys
We need to enable billing on our Chromium Project page, but the use of the API is then free.