Closed Bug 1560635 Opened 5 years ago Closed 5 years ago

Block autoplay SUMO page should be updated for Firefox 69

Categories

(support.mozilla.org :: Knowledge Base Content, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

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.

https://support.mozilla.org/en-US/kb/block-autoplay

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)

Type: defect → task
Component: General → Knowledge Base Content
Flags: needinfo?(jsavage)
Summary: Block autoplay SUMO page is out of date → Block autoplay SUMO page should be updated for Firefox 69

Thanks for informing me. I've added version 69 to our tool so we can start updating this article.

Flags: needinfo?(jsavage)

You can assign me to this bug. I'd be happy to make the changes to the article.

I've made the necessary changes to the article. This bug can now be marked as resolved.

I made a few edits to the pending revision that Wesley submitted. Joni, can you review?

Flags: needinfo?(jsavage)

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.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(jsavage)
Resolution: --- → FIXED

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.

See Also: → 1642507

(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.

(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]

[1] https://docs.google.com/document/d/1p81bYntlLMTxXoANnQXS9KH0TZ4y8aKKeH9x3GVS3eY/edit#heading=h.k3q4co83ntet

And how are users supposed to block autoplay so that it actually blocks autoplay? "Activated by user gesture" is toxic, because:

  1. 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.

  2. 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:

  1. 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.
You need to log in before you can comment on or make changes to this bug.