Create Geoclue2 Location provider
Categories
(Core :: DOM: Geolocation, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox102 | --- | fixed |
People
(Reporter: garvan, Assigned: mail)
References
()
Details
Attachments
(1 file)
Comment 1•9 years ago
|
||
Marking inactive due to the length of inactivity here, feel free to re-open if you wish this to remain active.
Comment 3•3 years ago
|
||
Doesn't look like I have permission to re-open, but I'd love to see this or some alternatively to allow integrating with any system geolocation methods I have set up, such as a Bluetooth GPS.
Assignee | ||
Comment 4•3 years ago
|
||
I do have a Geoclue2 geolocation provider for gecko-dev right now and have been using it in Firefox for a few weeks now.
This provider is purely (G)D-Bus based, so it doesn't need any additional external library as a dependency.
I envision it as a system-wide geolocation source, much like the ones that Firefox already uses on Windows, Mac OS or Android platforms.
Unfortunately, it's unlikely that I will be able to find enough time to go through a formal review process with this patch before this year winter holiday break.
Assignee | ||
Comment 5•3 years ago
|
||
Add a Geoclue (version 2) geolocation provider.
This way Firefox can make use of multiple location sources present in the
system, from GNSS provided by a cellular modem or the current network to
location based on visible WiFi networks and 3G tower data, all while
sharing them with other applications.
This is a pure D-Bus-based implementation using a proper state machine, it
does not require any additional dependencies.
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 6•3 years ago
|
||
By the way, WebKitGTK got Geoclue2 support already.
Comment 7•3 years ago
|
||
How does this compare to the portal service that was recently added for Flatpak and so on? Do we really need both?
Assignee | ||
Comment 8•3 years ago
|
||
(In reply to Emilio Cobos Álvarez (:emilio) from comment #7)
How does this compare to the portal service that was recently added for Flatpak and so on? Do we really need both?
Portal service is a limited API for Flatpak containers that internally forwards to Geoclue. Without Flatpak runtime that API is not available.
In contrast to the portal provider this is a complete, native Geoclue API implementation on a state machine (for handling corner cases, etc.) for use in a standalone Firefox.
Comment 10•3 years ago
|
||
Backed out for causing bustages at GeoclueLocationProvider.
Backout link: https://hg.mozilla.org/integration/autoland/rev/7f6113218f5598eafb379c8d0968fd3976c746f9
Failure log: https://treeherder.mozilla.org/logviewer?job_id=378119283&repo=autoland&lineNumber=178368
Comment 11•2 years ago
|
||
Sylvestre, do you know why reviewbot didn't complain about the static analysis issue in the phab revision? I'm pretty sure it used to do that in the past.
Comment 12•2 years ago
|
||
Marco and Andi should know better now
Comment 13•2 years ago
|
||
Comment 14•2 years ago
|
||
bugherder |
Comment 15•2 years ago
|
||
There is an intermittent issue with code-review events, and it doesn't notify Phabricator, we are tracking this in github.
Description
•