Selection by the user to deny notification permissions is not properly reflected in Private Browsing Mode
Categories
(Firefox :: Site Permissions, defect, P3)
Tracking
()
People
(Reporter: emz, Unassigned)
Details
(Keywords: reporter-external, sec-other)
T1-1 : In Firefox on Windows, Linux, and macOS, the selection by the user to deny notification permissions is not properly reflected in Private Browsing Mode. Specifically, in Private Browsing Mode, when a user selects to deny notification permission, the permission status will be set to “default” not “denied”.
This bug is from the report in Bug 1784741.
| Reporter | ||
Comment 1•4 years ago
|
||
All permissions in private browsing mode are ephemeral. This is intended behavior.
Temporary permissions are not exposed via the Permissions API. There is an existing bug for that, which I can't find right now.
Does "default" and "denied" refer to the Permissions API?
Comment 2•4 years ago
|
||
Thank you for reviewing our report.
We used the Notification API to get the permission state “default” not the Permissions API.
You can reproduce this by following these steps.
- launch the Firefox browser
- Open a website (https://permission.site) in Private Browsing mode)
- Click notification button on the website to receive the notification permission request.
- The website requests Notification permission
- Click “Block” button on the permission request prompts
- Open “Browser Console” from “Inspect”
- Input “Notification.permission” and Enter.
- Check returned value (You can see value “default” not denied)
Comment 3•4 years ago
|
||
The severity field is not set for this bug.
:pbz, could you have a look please?
For more information, please visit auto_nag documentation.
| Reporter | ||
Comment 4•3 years ago
|
||
I can reproduce this issue. It seems unexpected, but I'm not sure if it needs to be a sec-bug. The permission prompt simply shows again when the site requests permission the next time. Since the API is user-activation gated I don't see a high risk of abuse here. Maybe I'm missing something though? Dan, do you agree?
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 5•3 years ago
|
||
Here is the code that sets the temporary permission if in PBM. This temporary permission doesn't seem to be exposed via the Notification API currently. https://searchfox.org/mozilla-central/rev/a3decf626dabd89620171f0ea7840cc4351fe218/browser/modules/PermissionUI.jsm#1120-1121
Comment 6•3 years ago
|
||
I agree: this is a bug, but not a security bug. Leaving hidden for now because it's related to other issues in the same report, but that may not be necessary.
Updated•3 years ago
|
Updated•2 years ago
|
Description
•