Dear Maintainer,

firefox (and chrome, and presumably a few other programs) use DBus ScreenSaver endpoints to signal idle-inhibition status. swayidle only listens for systemd/logind inhibit messages. This causes disruptive screensaver/lock activation during video playback or video calls.

https://github.com/swaywm/swayidle/pull/164 contains a patch that implements the ScreenSaver endpoint in swayidle to listen to the applications' inhibit signalling, solving the problem.

Please pull in the patch to fix!

Regards, David