Bug 264320
| Summary: | Explain revoked push subscriptions via a console message | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Karl Dubost <karlcow> |
| Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 17 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Karl Dubost
When a push subscription is being revoked, notify the web developer by placing something in the Web Inspector console.
Perhaps a message could also be sent to the Reporting API.
> When a permission is revoked, the user agent MAY fire the "pushsubscriptionchange" event
> for subscriptions created with that permission, with the service worker registration
> associated with the push subscription as registration, a PushSubscription instance
> representing the push subscription as oldSubscription, and null as newSubscription.
> The user agent MUST deactivate the affected subscriptions in parallel.
see https://w3c.github.io/push-api/#security-and-privacy-considerations
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Karl Dubost
<rdar://114794666>