Closed Bug 1680828 Opened 3 years ago Closed 3 years ago

Blocking Autoplay and Cosmetic Animations and Setting Reduced Motion does not Black Autoplaying Marquees

Categories

(Core :: DOM: Core & HTML, defect)

Firefox 83
defect

Tracking

()

RESOLVED FIXED
86 Branch
Tracking Status
firefox86 --- fixed
firefox87 --- affected

People

(Reporter: erwinm, Assigned: emilio)

References

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Visited www.kickstarter.com

Actual results:

Got hit with animated marquee text, migraine, nausea.

Expected results:

User settings to block autoplay should be able to block autoplaying marquees, carousels, punches to the eyes, punches to the back of the head, smooth scrolling, and other animation.

duplicate of bug 161109

Hi,

Indeed, this seems to be a duplicate of bug 161109, but that issue is pretty old. Further, I will move this over to a component so developers can take a look over it and make a decision about this. If this is not the correct component please feel free to change it to an appropriate one.

Thanks.

Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core
See Also: → 161109

We should disable marquee when prefers-reduced-motion computes to true.

Component: CSS Parsing and Computation → DOM: Core & HTML
Flags: needinfo?(emilio)

So looking a bit harder about this, we could address this easily adding (prefers-reduced-motion) to this rule, but that won't cut it if the content inside the marquee is actually wider than the available space.

Would something like that:

.horizontalOuterDiv { margin: 0 !important; padding: 0 !important; }

in a user stylesheet do what you want? We could put that behind a pref or something if you think that'd be something common, but making content not reachable by default might be a no-go, not sure.

Flags: needinfo?(emilio) → needinfo?(erwinm)

If it's stopped and cut off, at least part of it is readable.

If it's allowed to run as coded, then for me the marquee is unreadable, and the rest of the screen may be unreadable, and anything near the screen may be unreadable, and pain.

Flags: needinfo?(erwinm)
Assignee: nobody → emilio

(In reply to MarjaE from comment #5)

If it's allowed to run as coded, then for me the marquee is unreadable, and the rest of the screen may be unreadable, and anything near the screen may be unreadable, and pain.

Right, my point is that you could have a user stylesheet disabling the animation, or at least I don't see why you wouldn't. But anyhow I'll send a patch to make this automatic, I think it's probably fine.

Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/44b10d5d64ed
Auto-disable marquee scrolling when (prefers-reduced-motion) evaluates to true. r=bgrins
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
Blocks: 1700599

Still not fixed in Firefox 87.

Another affected page https://tank100.com/tanks/tank-armament-first-world-war/

Summary: Blocking Autoplay and Cosmetic Animations Does not Block Autoplaying Marquee on Kickstarter → Blocking Autoplay and Cosmetic Animations and Setting Reduced Motion does not Black Autoplaying Marquees

(In reply to MarjaE from comment #10)

Another affected page https://tank100.com/tanks/tank-armament-first-world-war/

That is not a marquee, that's just a div changed with JS, so not much we can do there it seems.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: