[Webkit-unassigned] [Bug 257889] New: Permissions API reports wrong permissions for notifications

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 9 08:25:12 PDT 2023


https://bugs.webkit.org/show_bug.cgi?id=257889

            Bug ID: 257889
           Summary: Permissions API reports wrong permissions for
                    notifications
           Product: WebKit
           Version: Safari 16
          Hardware: All
                OS: macOS 13
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: cj at pushly.com

# Overview

After denying permission status for notifications, leaving the site, and returning to the site the Permissions API (and window["Notifications"].permission) incorrectly reports that the visitor is not in Deny status.

# Steps to Reproduce:

* Visit: https://web-push-book.gauntface.com/demos/notification-examples/
* Click the switch to prompt for enabling push notifications
* Choose to deny notifications
* Close the browser tab
* Open a new tab and re-visit https://web-push-book.gauntface.com/demos/notification-examples/
* In console run:
** `window["Notification"].permission` - reports "default" when should be "denied"
** `navigator.permissions.query({name: "notifications"}).then(p => { console.log(p.state) })` - reports "prompt" when should be "denied"
* Note that in Safari Preferences -> Websites -> Notifications that "Deny" is shown for web-push-book.gauntface.com

# Expected Results:

The permission status should properly report that the visitor's notification permission is in Deny status

# Actual Results:

The permission status reports that visitor's notification permission is in a promptable state / not in Deny status

# Version Information:

Safari browser version: 16.6
Operating system: macOS Ventura 13.5

# Additional Information:

Likely related to: https://bugs.webkit.org/show_bug.cgi?id=257710

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230609/f463861b/attachment-0001.htm>


More information about the webkit-unassigned mailing list