Sorry, to be clear: "if a user disables push notifications [in the Android UI]..."

Anita's (implicitly) adding this with her work on site notification channels for Android O. We'll have to keep that in mind when migrating WebAPKs to channels.

For Android pre-O, there's two things to do:
  - For WebAPKs, revoking notification permission for the app should be analogous to revoking permission for the origin. That's safe and simple.
  - For regular Chrome, we need to decide what to do when revoking notification permission for the app. Dropping *all* push subscriptions is an option, but then we lose our metrics on how many people have disabled notifications on the app-level.

It's possible that some people might temporarily turn off notifications for Chrome, with the intention of turning them on again later and still receiving push notifications from their existing subscriptions. Even if that is the case though, we should probably unsubscribe them, then deliver a pushsubscriptionchange event if the user re-enables notifications.

> Dropping *all* push subscriptions is an option, but then we lose our metrics on how many people have disabled notifications on the app-level.

Presumably we could just use metrics that log once per startup instead of once per incoming push message.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot