New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 764252 link

Starred by 3 users
Status: Duplicate
Merged: issue 773751
Owner: ----
Closed: Oct 2017
Cc:
dominickn@chromium.org
█ owe...@chromium.org
█ awdf@chromium.org
█ sbirch@chromium.org
peter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Removing a homescreen icon does not disable notifications

Project Member Reported by stillers@chromium.org, Sep 12 2017 
Chrome Version: All
OS: Android

What steps will reproduce the problem?

(1) Install an application (via A2HS) that sends notifications such as mobile.twitter.com.
(2) Enable push notifications.
(3) Remove/uninstall the app.

What is the expected result?

Push notifications are not received/displayed.

What happens instead?

Push notifications appear.

Comment 1 by peter@chromium.org, Sep 12 2017

Cc: dominickn@chromium.org awdf@chromium.org owe...@chromium.org
Status: Available (was: Untriaged)
This is the expected behaviour for the regular Add to Homescreen -- they're effectively just bookmarks. AFAIK we still can't be certain about whether they're still on the homescreen.

It's a bit more complicated for WebAPKs. Issues 666838, 643476 and  685806  capture some of the difficulties: because Chrome maintains its own permission registry, we have to be very careful to not create an inconsistent experience.

I'm leaving this open because there is one interesting case that we don't currently address: the user *disables* notifications for the WebAPK and then uninstalls it. This will cause notifications to show up again: they're blocked by the WebAPK package prior to the uninstall, but will be shown by the Chrome package after the uninstall. That's definitely not expected.

Comment 2 by dominickn@chromium.org, Oct 11 2017

Mergedinto: 773751
Status: Duplicate (was: Available)
►

Sign in to add a comment