New issue
Advanced search Search tips

Issue 603237 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

chrome.notifications on ChromeOS priority granularity missing

Reported by kgra...@gmail.com, Apr 13 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Platform: 7834.70.0 (Official Build) stable-channel veyron_minnie

Steps to reproduce the problem:
1. chrome.notifications.create('test-123',{priority:0,title:"title",message:"message",iconUrl:'/ico-128.png',type:'basic'})
2. chrome.notifications.create('test-456',{priority:1,title:"title",message:"message",iconUrl:'/ico-128.png',type:'basic'})
3. chrome.notifications.create('test-789',{priority:2,title:"title",message:"message",iconUrl:'/ico-128.png',type:'basic'})

What is the expected behavior?
In previous versions of Chrome (last 49 stable release?) a priority 2 notification should pop to the foreground so the user can see it right away.

What went wrong?
Priority 2 notifications do not appear to the user, but instead only a small icon indicating that there is a notification appears near the clock. There is no difference between a priority 0, priority 1 and priority 2 notification.

WebStore page: 

Did this work before? Yes Last Chrome 49 release I believe

Chrome version: 49.0.2623.112  Channel: stable
OS Version: 7834.70.0
Flash Version: Shockwave Flash 21.0 r0

On other platforms, Windows, Mac, the notifications do appear visible to the user right away.
 
Cc: peter@chromium.org
peter does that ring a bell?

Comment 2 by kgra...@gmail.com, Apr 14 2016

Strange, I rebooted and now they are working fine again. I will try and determine how to reproduce.

Comment 3 by peter@chromium.org, Apr 15 2016

Negative, I'm not aware of any changes in this area after Chrome 47. kgraehl, please let us know if it happens again?
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 17 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment