SUMMARY Popup hide setting does not honour browsers' `requireInteraction: true` property on desktop notifications. Additionally, if the web app intends to close the notification by itself, after a timeframe longer than KDE plasma's 'hide after' setting, It is not given such an opportunity. I imagine the second issue cannot be resolved - as it not known whether the app intends to do so, Plasma would have to leave the notification open indefinitely, in order to give the app the chance to close it, so... That is not something I expect could be resolved (although, maybe it could be, and if you're very clever, please feel free! :) Perhaps by using the browser integration, the javascript could be parsed for a call to close() on the notification object? Seems very difficult.) The first issue however, should be resolvable, since it is known at the time of creation of the notification that it is intended to stay there until interaction occurs. STEPS TO REPRODUCE 1. Use this site to demonstrate: https://googlechrome.github.io/samples/notifications/requireInteraction.html 2. Click the "show notifications" button. 3. Observe two desktop notifications, one which should automatically disappear within Plasma's set timeframe, one which should remain visible until it is cleared by the user. OBSERVED RESULT See both notifications be hidden, without interaction EXPECTED RESULT One should be hidden after the set timeout, the other should require user interaction to hide. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION
On plasma 6, this works as expected when using the firefox browser -- the requireInteraction: true notification does not automatically close. What browser are you using?
I tested using google chrome on plasma 6 and this still works -- the requireInteraction: true notification does not automatically close. So I believe that has been fixed. Feel free to reopen if you still have this issue on plasma 6!
Did you test in Wayland? I was using FF and chrome here, but it's Plasma 5 Wayland, so if it's not fixed in Wayland in Plasma 6 there might still be an issue, but if you tested in Wayland too, yeh I agree, fixed in 6! (hey that rhymes, that should be a slogan or something hahaha)
(In reply to pallaswept from comment #3) > Did you test in Wayland? I was using FF and chrome here, but it's Plasma 5 > Wayland, so if it's not fixed in Wayland in Plasma 6 there might still be an > issue, but if you tested in Wayland too, yeh I agree, fixed in 6! (hey that > rhymes, that should be a slogan or something hahaha) Yes I was testing on wayland.
> Yes I was testing on wayland. Wonderful! Fixed in 6! Thanks for looking into it and testing it out so quickly! Enjoy the rest of your week :)