onClicked and onClosed events are fired wrong for native Mac OS notifications
Reported by
ser...@mstone.com.au,
Today
(2 hours ago)
|
|
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36
Steps to reproduce the problem:
The code should be executed in background.js script
chrome.notifications.onClicked.addListener((id) => {
console.log('onClicked', id);
});
chrome.notifications.onClosed.addListener((id) => {
console.log('onClosed', id);
});
chrome.notifications.create('test', {
type: 'basic',
title: 'Test',
message: 'Lorem Ipsum',
requireInteraction: true,
iconUrl: 'images/private192.png'
});
What is the expected behavior?
1) A new notification should be created.
2) A click on a non-button area should create a record in console "onClicked test"
3) A click on Close button should create a record in console "onClosed test" and delete notification.
What went wrong?
OK - If the Close button is clicked first then onClosed event is fired.
WRONG - If the non-button area clicked first then any following click on Close button fires another onClicked event instead of onClosed event.
In other words, onClosed event is not fired if a non-button area was clicked first.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 71.0.3578.98 Channel: beta
OS Version: OS X 10.14.3
Flash Version:
This issue exists only for native macOs notifications.
If Chrome flag #enable-native-notifications is set to Disable events are fired as expected.
|
|
►
Sign in to add a comment |
|
Comment 1 by ser...@mstone.com.au
, Today (107 minutes ago)