Avainsanana Twitch
Does not appear to have been fixed by Firefox 88
Hi Alex!
It does not appear to have been fully fixed by Firefox 88 for me at least, although the conditions have changed slightly, and the remaining broken behavior is now slightly different too.
First, to update my note above: media.autoplay.enabled.user-gestures-needed has been superseded by media.autoplay.blocking_policy, and setting the latter to 2 is now required to trigger the issue (as it manifests presently); with the setting at either 0 or 1 I haven’t been able to reproduce any variation of the issue.
Now, the video doesn’t get paused anymore, but the unmuting also does not work: clicking the muted indicator just always resets it back to muted, instead of actually unmuting.
Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)
After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service.
== Steps to reproduce ==
1. Follow the steps in [1] to enable VA-API.
2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play
== What I expect to happen ==
For the video be played without issues (as it did with Firefox 78).
== What happens ==
After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch) or (Youtube). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears.
== Other info ==
A fix is apparently already in the works upstream [2].
* [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/
* [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671
Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1
With `media.autoplay.enabled.user-gestures-needed` set to false and `media.autoplay.default` set to 1 (block audio), which is the default (and other autoplay-related settings in their defaults as well), a Twitch video can only be either paused or playing muted; unmuting the video pauses it and vice versa.
== Steps to reproduce ==
1. Open about:config
2. Search for autoplay in the settings
3. Set media.autoplay.enabled.user-gestures-needed to false
4. Set media.autoplay.default to 1
5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
6. Try to unmute the video
== What happens ==
The video is unmuted, but also paused
== What I expect to happen ==
For the video to continue playing, unmuted
I’m able to reproduce this when I set media.autoplay.enabled.user-gestures-needed to false
I’m able to reproduce this when I set media.autoplay.enabled.user-gestures-needed to false; if set to true (which is the default), unmuting does not pause the video.
Obnoxiously loud (Finnish) Weekend Festival ad
The Report button doesn’t seem to do anything for the one ad I’ve reported dozens of times by now: please do something about the obnoxiously loud (Finnish) Weekend Festival ad. Like I said, I’ve already reported it as such countless times using the report button, but Twitch still keeps playing it to me.
I don’t mind ads per se, but I’m now seriously contemplating installing an adblocker just because of this one ad.
Steps to reproduce
media.autoplay.defaultto1(”Block Audio”, which is the default)media.autoplay.blocking_policyto2What I expect to happen
For the audio to be unmuted.
What happens instead
The audio remains muted, and the volume control/indicator remains in the muted position.
I’m unmotivated to report this to Twitch, as I’m unsure about the precise meaning of
media.autoplay.blocking_policy, and I currently don’t use the non-working value for it myself. Feel free to downprioritize this as you see fit, unless the original reporter is still affected. Here’s my downstream report over at Launchpad though, just for reference. (I’ll update it too.)