Block autoplay SUMO page should be updated for Firefox 69
Categories
(support.mozilla.org :: Knowledge Base Content, task)
Tracking
(Not tracked)
People
(Reporter: alwu, Unassigned)
References
()
Details
After landing bug1543812, the block autoplay has different setting, its related SUMO page [1] should be updated to catch up with the current implementation.
Comment 1•5 years ago
|
||
Bug 1543812 is fixed in Firefox 69. I'll Need Info Joni, since Firefox version 69 isn't yet available in the "Customize this article" tool.
Related discussion:
https://support.mozilla.org/en-US/kb/block-autoplay/discuss/8002 [Fx69] New autoplay options to allow or block both audio and video (Bug 1543812)
Updated•5 years ago
|
Thanks for informing me. I've added version 69 to our tool so we can start updating this article.
Comment 3•5 years ago
|
||
You can assign me to this bug. I'd be happy to make the changes to the article.
Comment 4•5 years ago
|
||
I've made the necessary changes to the article. This bug can now be marked as resolved.
Comment 5•5 years ago
|
||
I made a few edits to the pending revision that Wesley submitted. Joni, can you review?
Thank you, Wesley and Alice for editing this article. I've reviewed it and will now close the bug. We'll mark it for localization when we get a little closer to release.
The instructions ask users to scroll down to certain preferences. If we need to page down instead, about:preferences still goes haywire due to focus bugs. The instructions do not include alternatives for users who cannot scroll in general or on about:preferences.
The instructions also state that "The Block Audio and Video setting will prevent autoplay for all media, including video, even though audio is muted." Which is not true.
Comment 8•4 years ago
|
||
(In reply to MarjaE from comment #7)
The instructions ask users to scroll down to certain preferences. If we need to page down instead, about:preferences still goes haywire due to focus bugs. The instructions do not include alternatives for users who cannot scroll in general or on about:preferences.
The instructions also state that "The Block Audio and Video setting will prevent autoplay for all media, including video, even though audio is muted." Which is not true.
I opened a new bug 1642507 to address those issues.
Reporter | ||
Comment 9•4 years ago
•
|
||
(In reply to MarjaE from comment #7)
The instructions also state that "The Block Audio and Video setting will prevent autoplay for all media, including video, even though audio is muted." Which is not true.
This is partially true, because it indeed blocks all media, but it only happens before the page gets activated by user gesture. [1]
Comment 10•4 years ago
|
||
And how are users supposed to block autoplay so that it actually blocks autoplay? "Activated by user gesture" is toxic, because:
-
Allowing "gestures" to activate the video or other online migraine delivery system makes it unclear how not to, because we don't know which ones will activate it.
-
Relying on "gestures" creates a situation where even if we know the triggers, users with various disabilities and/or alternative controls not be able to avoid it or not be able to activate it. Relying on "tapping" creates similar problems.
I can't check the linked article because:
- It's on Google Docs, so the text is unreadable, the text animates scrolling after each page down, which is one of my migraine triggers, and the site combines that with a non-scrolling sidebar which is another.
Description
•