FS#50284 - [firefox] Slock activates while playing fullscreen HTML5 video

Attached to Project: Arch Linux
Opened by Victor Engmark (l0b0) - Saturday, 06 August 2016, 16:46 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 13 August 2016, 16:50 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Evangelos Foutras (foutrelis)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When playing for example YouTube videos in fullscreen mode the screensaver timeout is still active.

Additional info:

$ slock -v
slock-1.3, © 2006-2016 slock engineers
$ firefox -version
Mozilla Firefox 48.0
$ xset q
[…]
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 600 cycle: 600

Steps to reproduce:

1. Enable slock (see https://github.com/l0b0/tilde/blob/c0e34f86b3893e0815fea4afe3af7f545228d4ee/.xprofile#L59)
1. Start Firefox
1. Start playing a YouTube video which has a runtime of more than 10 minutes
1. Fullscreen the video
1. Wait for 10 minutes
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Saturday, 13 August 2016, 16:50 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Sunday, 07 August 2016, 04:44 GMT
Is it not supposed to?
Comment by Victor Engmark (l0b0) - Sunday, 07 August 2016, 13:23 GMT
I may have the wrong end of the stick here, because I realise it's probably the job of the *application* to disable the screensaver while running in fullscreen mode. If that's the case, would it be possible to reassign this bug to Firefox?

That said, I can't see that there's a fundamental difference between watching a fullscreen video in Firefox and using for example VLC, SMPlayer or any other application which shouldn't be interrupted by a screensaver while in fullscreen mode.

Edit: Looks like the relevant bug is <https://bugzilla.mozilla.org/show_bug.cgi?id=1168090>. You can probably just close this one.
Comment by muchweb (muchweb) - Thursday, 11 August 2016, 11:00 GMT
AFAIK slock doesn't start on it's own. It is used it in combination with some other program, like xautolock.
Comment by Jan Alexander Steffens (heftig) - Saturday, 13 August 2016, 16:50 GMT
It is not Firefox' job to know about every single lockscreen implementation. Firefox already uses the org.freekdesktop.ScreenSaver D-Bus service to inhibit screensavers. It is slock's job to support this.

https://people.freedesktop.org/~hadess/idle-inhibition-spec/index.html

Loading...