Permissions granted e.g. in Private windows won't be saved upon exit. If you're on the site asking you the permissions, if you click on the "knobs" button next to the shield icon, does it list any?

This is happening on every Google search or any site that is asking for location permission and has been previously granted or even in the moment it's asking, I'm granting it permission & checking "remember this decision", closing the window, and coming back. Not using InPrivate.

The prompt says "Allow www.google.com to access your location? This will open your system location settings. Please grant location permission to Firefox" and there's a checkbox to remember + an allow or block button. (This is when it's Google requesting the permission of course. It changes the URL depending on the site.)

1) It's not opening my systems location settings, so that's broken.

As to your question, when I click on the little settings slider widget to the left of the domain name, there is only the "Access your location" setting present, and it's set to "Allowed".

OK so it's the macOS not granting the permission.

It might be that once denied in the past, the system Settings deeplink won't be allowed to trigger anymore and you have to go to grant that manually. (I can try researching open bugs for that dialog, or its wording if that's no longer the action invoked.)

Do you know how to go to your System Settings and enable it there? (My version has it in "Privacy & Security" › "Location Services" pane.)

What version of macOS you're running, if you don't mind?

I've never denied Firefox location permission from the moment it was installed on my Mac Studio and MacBook Pro.

I've recently gone into (recently as in last night) and switched location off for Firefox, then turned it back on, as well. And it doesn't change behavior in the app.

Latest public version of Sequoia. 15.7.7.

Very strange bug.

Huh that's weird, however sounds like it's happening: https://bugzilla.mozilla.org/show_bug.cgi?id=2041844 (I originally read the bug as "Tahoe"–only, hence why I asked again, but re–reading it it indeed sounds like Sequoia–only.)

Depending how comfortable you are providing some debugging info on the bugzilla ticket, would you like to perhaps comment on the bug if you can assist in capturing some logs to help understanding the error? Thanks!

I've replied to the bug, thanks for the link. What can I do to give debug/diagnostic info?

Wonderful. Now when you're in the contact list for the bug, you'll get updates on the timeline, so if the engineers who are familiar with the underlying issue have any idea for a good logging procedure to help them figure how to even e.g. start reproducing, they might reach out to you for assistance.

This has started cropping up quite recently, and given it's only on the specific later cycle patch versions of 15.7.6+ possibly, it's still in early stages of investigation, so it might not appear to "move too fast" — but now being on the "carbon copy" you'll get pinged with changes. Thanks for the help!