Geolocation not working (Firefox, Chromium)

[davydm]

I've noticed that geolocation doesn't work on either Firefox (64.0) (*) or chromium (71.0.3578.80) but does work in google-chrome (71.0.3578.9, which suggests that there's a USE flag that I'm missing for both locally-compiled browsers; however `equery u firefox` and `equery u chromium` don't seem to show any flags specific to geolocation.

What am I missing?

I need geolocation for the work I'm doing and I'd much rather not have google's binaries installed on my machine.

(*) specifically, the error handler for navigator.getCurrentPosition is invoked with the message "Unknown error acquiring position", which doesn't really narrow it down; and yes, I do allow location requests on the pages I'm testing on.

[bunder]

My understanding is that the location stuff in browsers works based on your external (if you're behind a router) ip address to find out what isp you're using, then make an educated guess about where you might be. Websites often get it wrong for me, sometimes up to 100km away.

edit: google does some shady stuff on android with gps and wifi access point scanning to map and triangulate a little more accurately, at the cost of privacy. not sure if they do the same thing on pc-based chrome.
_________________

[davydm]

I'm quite sure you're right about the "how" of geolocation on desktop browsers.

TBH, for my current needs, I don't need it to be accurate -- I just need any sort of answer, since I'm developing against the user's current location. Google Chrome, for instance, reports me about 10km away from where I really am, but it's better than no answer at all. Although, for my users, I guess they'd like some semblance of accuracy: geolocation is used to determine which restaurants in our catalog are in their area, and hence, which restaurants they can order from. Obviously, with no result, we have no idea what restaurants to recommend to the user, so I get an empty list :/

Whilst I also accept that Google Chrome may just be doing super-dodgy stuff behind my back, if there is something I can do to fix this for other browsers, I'd still be interested (:

[Avg_Surfman]

Sorry for the necro, but this is still an issue. Unfortunately, this popped up during a CTF contest, and I was not able to fiddle with geolocation flags.
This also happens on flatpaked chromium, but NOT chrome (which actually returns a geolocation instead of timing out!).
I'm convinced this is Gentoo-specific because this reportedly works on Ubuntu 24.04.

EDIT: Found out that MLS has been shutdown this year :/ .


This is also the only result on the forums with the same issue.