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

Issue 779281 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Opening a client in response to notification action tap from lock screen doesn't hide the lockscreen and focus Chrome

Project Member Reported by owe...@chromium.org, Oct 28 2017

Issue description

At CDS it was reported to me that someone is using notification actions, but found that when tapping them from the lock screen, that Chrome is opened "in the background" but the lockscreen just stays there instead of hiding.

I recall a bug like that occurring a while ago where the notification shade itself didn't hide in response to tapping an action, I wonder if this is related / known?

(FYI not marking as Available since I haven't reproduced) 
 

Comment 1 by awdf@chromium.org, Oct 30 2017

Status: Unconfirmed (was: Untriaged)
Not heard of this. Think we would need more info / a video ideally to debug.

Comment 2 by peter@chromium.org, Oct 30 2017

Status: Available (was: Unconfirmed)
Reproduction steps:

1. Show a notification with an action button. The button should create or focus a tab when activated.
2. Minimise Chrome.
3. Lock the device.
4. On the lockscreen, expand the notification and click on the action button.

Expected result:

Requested to unlock the device (if necessary) after which the Chrome tab is brought to the foreground.

Observed result:

The notification disappears. After manually unlocking the device, the Chrome tab is in the foreground.
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 30

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Sign in to add a comment