MSIX location permission is persistent after tab closing
Categories
(Core :: DOM: Geolocation, defect)
Tracking
()
People
(Reporter: windfreaker, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0
Steps to reproduce:
Only tested with Microsoft Store's MSIX build. The bug was noticed as the Windows 11 taskbar will alert when location permissions are being used. In Firefox 99 the location permission alert will persist even after the tab using the device's location is closed.
I am reporting this bug as a user will often leave the browser open for hours, later see that it is requesting location permissions long after the user last authorized it, and grow concerned for their security.
- Open Google Maps (https://www.google.com/maps/)
- Provide location permission
- Wait for taskbar icon to appear
- Close Google Maps tab
Actual results:
Icon showing location permission requested persists indefinitely (until the browser is closed).
Expected results:
The icon should go away as the browser is no longer accessing the device's location.
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Confirming this bug still exists in Firefox 100.
Comment 2•2 years ago
•
|
||
Moving this to Installer as that's where the MSIX bugs are, but this may be related to how location services work on Windows (they're behind a timeout).
Updated•2 years ago
|
Comment 3•2 years ago
|
||
(In reply to Gian-Carlo Pascutto [:gcp] from comment #2)
Moving this to Installer as that's where the MSIX bugs are, but this may be related to how location services work on Windows (they're behind a timeout).
Yeah, I don't think Desktop Integrations will be able to help much here. Can we get this in front of a location services person? I wonder if a Service Worker is subverting expectations here. :emilio, sounds like you might have some idea of who to redirect to here?
Comment 4•2 years ago
|
||
I guess if it is very win32 specific, even Widget: Win32
could be appropriate (which would send it right back to me).
Comment 5•2 years ago
|
||
Yeah, I'd look at whether WindowsLocationProvider::Shutdown
is being called and if not, why not.
Comment 6•2 years ago
|
||
The two patches in bug 1770126 fix this. I should've probably sent them here but I wasn't sure where the location badge was, so wasn't quite sure whether it'd actually fix this, but it does.
Comment 7•2 years ago
|
||
This bug is reproducible with the non-MSIX builds as well, fwiw, at least if I tweak the windows location settings to make Firefox use them.
Updated•2 years ago
|
Description
•