Contact emails [email protected]
Specification https://notifications.spec.whatwg.org Summary Chrome is rolling out notification attribution for installed Progressive Web Apps (PWAs) on macOS. When a PWA is installed on macOS, its notifications will now be natively attributed to the PWA itself (using its own name and icon in the Notification Center) rather than Google Chrome. This is primarily a UX change in how notifications are displayed to the user, aligning PWA notifications with native macOS applications. It does however introduce some small (although not directly web-exposed) behavioral changes as well. Both of these changes match the already shipping behavior in WebKit: - For installed PWAs, Chrome will no longer support the `requireInteraction` field for notifications. On macOS the choice for a notification being temporary vs persistent is a per-app setting controlled by the user rather than a per-notification setting controlled by the app. - Additionally the app badging API will now require notifications permissions for the app badge to show up. If notifications permission isn't granted the API will silently do nothing. Enterprise administrators who pre-grant notification permissions via policy must update their configurations if they want to keep that behavior for PWAs on macOS: In addition to the Chrome origin-based policy (NotificationsAllowedForUrls), administrators must deploy a macOS MDM configuration profile to pre-grant notification permissions to the PWA's specific bundle ID. Blink component UI>Notifications Web Feature ID notifications Risks Interoperability and Compatibility While this change makes slight changes to how the notifications and app badging APIs behave, the new behavior closely aligns with Safari's implementation, and thus is expected to not cause significant interoperability or compatibility risk. Gecko: No signal WebKit: Shipped/Shipping This change aligns the notifications and badging behavior for installed PWAs on macOS with how these APIs behave for installed web apps in Safari. Web developers: No signals Other signals: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? No information provided Debuggability No information provided Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? No Is this feature fully tested by web-platform-tests? No Tracking bug https://issues.chromium.org/issues/327449602 Launch bug https://launch.corp.google.com/launch/4312334 Estimated milestones Shipping on desktop 152 DevTrial on desktop 130 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5863296436666368 This intent message was generated by Chrome Platform Status. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a50136c.606b822d.87713.0025.GAE%40google.com.
