Bugzilla

(In reply to Daniel Holbert [:dholbert] from comment #12)
> 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.

Er, I wasn't quite right on "That's tracked in bug 1863853" -- strictly speaking, bug 1863853 is about a private-browsing-mode specific thing (though it might still be what's happening for you, if you happen to have `privacy.resistFingerprinting.pbmode` enabled (note the `.pbmode` suffix) *and* you have a private browsing window open, or you have Firefox configured to never remember history.

Anyway: I've now filed bug 1897251 on the more-straightforward problem of `privacy.resistFingerprinting` causing `layout.frame_rate` to be ignored.  As noted there, this is kind of things working-as-intended, since the whole point of `privacy.resistFingerprinting` is to make all users look as-similar-as-possible, which includes things like using a fixed refresh rate (since websites can measure the refresh rate).

(For now, you might consider un-setting `privacy.resistFingerprinting` if this is causing usability issues for you; it's mostly intended for the *extremely* privacy conscious use-cases, in particular TorBrowser, where any fingerprinting at all potentially creates an existential risk, to the point that usability can be sacrificed.  That's why it breaks stuff like this.  It is possible to create feature-by-feature exceptions to it, but that also creates a maintenance burden and I'm not sure what the folks who work on that feature will decide on that point.)

Having said all that: if you don't have any `resistFingerprinting` prefs enabled at all and you're still seeing this full-motion animation, please let me know and we can dig further and see if there's some other setting that's breaking layout.frame_rate here.

(In reply to Daniel Holbert [:dholbert] from comment #12)
> 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.

Er, I wasn't quite right on "That's tracked in bug 1863853" -- strictly speaking, bug 1863853 is about a private-browsing-mode specific thing (though it might still be what's happening for you, if you happen to have `privacy.resistFingerprinting.pbmode` enabled (note the `.pbmode` suffix) *and* you have a private browsing window open, or you have Firefox configured to never remember history.

Anyway: I've now filed bug 1897251 on the more-straightforward problem of `privacy.resistFingerprinting` causing `layout.frame_rate` to be ignored.  As noted there, this is kind of things working-as-intended, since the whole point of `privacy.resistFingerprinting` is to make all users look as-similar-as-possible, which includes things like using a fixed refresh rate (since websites can measure the refresh rate).

(For now, you might consider un-setting `privacy.resistFingerprinting` if this is causing usability issues for you; it's mostly intended for the *extremely* privacy conscious use-cases, in particular TorBrowser, where any fingerprinting at all potentially creates an existential risk, to the point that usability can be sacrificed.  That's why it breaks stuff like this.  It is possible to create feature-by-feature exceptions to it, but that also reduces its robustness and creates a maintenance burden and I'm not sure what the folks who work on that feature will decide on that point.)

Having said all that: if you don't have any `resistFingerprinting` prefs enabled at all and you're still seeing this full-motion animation, please let me know and we can dig further and see if there's some other setting that's breaking layout.frame_rate here.