(In reply to Chas Belov from comment #8) > I have a screen recording showing this but don't see a way to add it to this bug. There should be an "attachments" section just before your first bug-comment here, with an "attach new file" button. But in any case, I do see your attachment on the github issue ([here](https://github.com/metafizzy/flickity/issues/1305#issuecomment-2114305541)) so no pressure/need to attach it here. (In reply to Chas Belov from comment #11) > And confirmed there must be another setting I've done in about:config which works together with layout.frame_rate to produce the results I'm getting. If I launch a profile with the factory configuration then setting layout.frame_rate to 1 produces the results you are getting. Do you happen to have `privacy.resistFingerprinting` set to true? That does seem to make the animation full-speed here, on my system at least. That's tracked in bug 1863853.
Bug 1894842 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Chas Belov from comment #8) > I have a screen recording showing this but don't see a way to add it to this bug. There should be an "attachments" section just before your first bug-comment here, with an "attach new file" button. (Though maybe that disappears when the bug is closed, depending on your bugzilla account permissions.) But in any case, I do see your attachment on the github issue ([here](https://github.com/metafizzy/flickity/issues/1305#issuecomment-2114305541)) so no pressure/need to attach it here. (In reply to Chas Belov from comment #11) > And confirmed there must be another setting I've done in about:config which works together with layout.frame_rate to produce the results I'm getting. If I launch a profile with the factory configuration then setting layout.frame_rate to 1 produces the results you are getting. Do you happen to have `privacy.resistFingerprinting` set to true? That does seem to make the animation full-speed here, on my system at least. That's tracked in bug 1863853.