Thanks for this extension! It's been working great for me except for this minor issue:
The notifications always require interaction, even if I uncheck "Require interaction to dismiss notification?" and save the config.
I eventually figured out through trial and error that the problem, for my system at least, seems to be the hard-coded non-zero priority:
Here's the test case that I pasted into the Chrome dev console in the context of this extension's options page:
chrome.notifications.create("test0", {
type: "basic",
iconUrl: chrome.extension.getURL("images/icon-256.png"),
title: "test 0",
message: "priority 0",
priority: 0,
requireInteraction: false
});
chrome.notifications.create("test1", {
type: "basic",
iconUrl: chrome.extension.getURL("images/icon-256.png"),
title: "test 1",
message: "priority 1",
priority: 1,
requireInteraction: false
});
chrome.notifications.create("test2", {
type: "basic",
iconUrl: chrome.extension.getURL("images/icon-256.png"),
title: "test 2",
message: "priority 2",
priority: 2,
requireInteraction: false
});
On my system, only the one set to priority: 0
respects the requireInteraction: false
setting. The others require interaction regardless of the setting.
It could be something specific to my shell, if that priority value is being passed along by Chrome, but I haven't found any shell-level settings that cause requireInteraction
to be respected for PD notifications. Could we perhaps get an option to customize the priority value to work around this?
Extension version: 0.22
Chrome version: Version 81.0.4044.138 (Official Build) (64-bit)
OS: Ubuntu 20.04
Shell: KDE Plasma Shell