Bug descriptionNotification.permission (mdn) defaults to "granted", when all other browsers default to the string "default". It should only be "granted" once someone explicitly approves the notification permission for a website.
It's (probably) worth noting that this doesn't affect the actual permission - visiting a site and trying to send a notification to a user will still create the prompt asking the user to approve/decline notifications.
This can lead to a weird user experience if a website reads the Notification.permission value and only creates a notification if they've been granted permission. Trying to create a notification without permission will create a box asking the user to accept/decline the notification permission, which may not be what a website wants to happen.
Bug description
Notification.permission
(mdn) defaults to "granted", when all other browsers default to the string "default". It should only be "granted" once someone explicitly approves the notification permission for a website.It's (probably) worth noting that this doesn't affect the actual permission - visiting a site and trying to send a notification to a user will still create the prompt asking the user to approve/decline notifications.
This can lead to a weird user experience if a website reads the
Notification.permission
value and only creates a notification if they've been granted permission. Trying to create a notification without permission will create a box asking the user to accept/decline the notification permission, which may not be what a website wants to happen.To Reproduce
console.log(Notification.permission)
Expected behavior At step 5 of the above reproduction example, the string "default" should be printed
Screenshots N/A
Details:
Additional context I've only been testing this in a regular website, so I don't know if the issue exists in web workers.