Even if Chrome distributes a notification to a WebAPK whose notification is disabled, Android will disable the notification to be shown on the notification panel. We could add more checks for not sending the notification, but the existing mechanism sounds good enough to WebAPK. What do you think? 

Ideally if the user disables push for this WebAPK we would reflect that in the developer observable permission (I.e. Change it to denied). Not sure how technically complex that is though.

I'm going to take this off blocking since they key bit (that they aren't set) is satisfied by Android not allowing us to send the notifications. Agree that it would be good to reflect this in the permission but not a blocker for v0.

*that they aren't sent

Sam, is this bug still valid? I think that what we want to do for notifications has changed. I am unsure if we have any bugs for the new plan

Lower priority and unassigning - this needs some UX feedback on how to reflect it given that we could only show notifications are disabled but not make them editable

+Rebecca and Anita who have been thinking about this problem.

+chowse as your WebAPK designer (and will take over notifications after 59 branch) but sbirch@ might be able to confirm no UX is needed at the moment (talked to him a bit informally about it.)

This is a similar problem to the one we face in Android O where we plan to soon allow users to allow/block web notifications from particular sites at a system level using notification channels - see https://bugs.chromium.org/p/chromium/issues/detail?id=700377 . We need to show the permission state but not make it editable - what we're planning on doing there is instead linking through to Android settings from the existing UI when the user tries to toggle. I wonder if we could do a similar thing for Web APKs on all versions of Android.

Mocks for that if it's helpful:
https://folio.googleplex.com/chrome-ux/mocks/428-o-notifications/032317_Flow#%2F01_Comparison.png%3Fz=width

I'm having trouble picturing where in the WebAPK that notifications are disabled and not editable (I thought they'd be like an installed app and have notifications permissions listed in their app info page.)

I was talking about the notification permissions listed within Chrome's in-app site settings in #11 - indeed they would be editable from the web apk's system settings, I'd need to check whether we can link the user through to those from Chrome's in-app settings though.

I might not be up on the latest, but I believe once you install a WebAPK, the site you installed it from continues to exists separately. The permissions between the two can be different, and editable individually. This leads to messiness if you change permissions in one spot but not the other, but at least both are still editable.

sbirch - is that correct or am I out-of-date there?

Removing myself and letting chowse@ take it from here!

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