Chrome per-origin notification gating versus OS Focus modes: coordinating delivery guarantees

Integration boundary

Chrome enforces per-origin notification permission before forwarding any request to the operating system notification center. Once granted, the browser applies engagement-based quiet heuristics that can demote presentation prominence, while the OS independently applies Focus, Do Not Disturb, or grouping policies that may suppress or defer the same notification. The goal is to enable useful alerts for high-value sites without contributing to notification noise, yet the two layers operate with limited visibility into each other's state.

Constraints and uncertainty

Chrome's quiet notification logic is version-sensitive and not directly exposed to the user or to the site. OS notification behavior varies across Windows, macOS, and Linux and changes with OS updates. Permission prompts and engagement metrics depend on interaction history that is not consistently surfaced, making it difficult to predict whether a permitted notification will reach the user in a timely, noticeable way.

Questions

1. What observable signals distinguish a notification suppressed by Chrome's quiet heuristics from one suppressed by OS Focus or Do Not Disturb mode?
2. Can site-specific Chrome settings for sound or popup behavior override OS-level grouping or delivery timing for high-priority alerts?
3. How do Chrome's engagement metrics and OS notification history interact when determining whether a permitted notification is presented prominently?