(This is similar to bug 1863853, but bug is specifically about private-browsing-vs-regular-browsing leakage. This one is more direct.) STR: 1. Start Firefox with a fresh profile. 2. (optional) Visit some page with CSS animations (e.g. [this MDN page](https://developer.mozilla.org/en-US/docs/Web/CSS/animation)) and confirm that the animation is smooth 3. Visit `about:config` and set `layout.frame_rate` to `1`. 4. Visit the page from step 2 and confirm that the animation is not-smooth. 5. Visit `about:config` and set `privacy.resistFingerprinting` to `true` 6. Visit the page from step 2 again. ACTUAL RESULTS: Animation is smooth again. EXPECTED RESULTS: Animation should still be not-smooth; or, users should perhaps have a way to make it not-smooth (perhaps some additional preference to let the frame-rate be an allowable fingerprinting target). As noted in bug 1863853 comment 7, `resistFingerprinting` isn't really a supported configuration and it's known to reduce usability (in the service of making every user look as similar as possible, which is the point of the pref). However, given that some users use `layout.frame_rate` for a11y purposes, maybe it's worth adding an additional about:config option to let that preference be honored even with `resistFingerprinting` enabled? (Side note for testing this: if you happen to be using Linux with Wayland, you may run into bug 1771017 which makes `layout.frame_rate` have no effect at all. You can avoid that by running `export MOZ_ENABLE_WAYLAND=0` before starting Firefox from your terminal, per bug 1863853 comment 0.)
Bug 1897251 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(This is similar to bug 1863853, but bug is specifically about private-browsing-vs-regular-browsing leakage. This one is more direct.) STR: 1. Start Firefox with a fresh profile. 2. (optional) Visit some page with CSS animations (e.g. [this MDN page](https://developer.mozilla.org/en-US/docs/Web/CSS/animation)) and confirm that the animation is smooth 3. Visit `about:config` and set `layout.frame_rate` to `1`. 4. Visit the page from step 2 and confirm that the animation is not-smooth. 5. Visit `about:config` and set `privacy.resistFingerprinting` to `true` 6. Visit the page from step 2 again. ACTUAL RESULTS: Animation is smooth again. EXPECTED RESULTS: Animation should still be not-smooth; or, users should perhaps have a way to make it not-smooth (perhaps some additional preference to let the frame-rate be an allowable fingerprinting target). NOTE: As noted in bug 1863853 comment 7, `resistFingerprinting` isn't really a supported configuration and it's known to reduce usability (in the service of making every user look as similar as possible, which is the point of the pref). However, given that some users use `layout.frame_rate` for a11y purposes, maybe it's worth adding an additional about:config option to let that preference be honored even with `resistFingerprinting` enabled? (Side note for testing this: if you happen to be using Linux with Wayland, you may run into bug 1771017 which makes `layout.frame_rate` have no effect at all. You can avoid that by running `export MOZ_ENABLE_WAYLAND=0` before starting Firefox from your terminal, per bug 1863853 comment 0.)
(This is similar to bug 1863853, but bug is specifically about private-browsing-vs-regular-browsing leakage. This one is more direct.) STR: 1. Start Firefox with a fresh profile. 2. (optional) Visit some page with CSS animations (e.g. [this MDN page](https://developer.mozilla.org/en-US/docs/Web/CSS/animation)) and confirm that the animation is smooth 3. Visit `about:config` and set `layout.frame_rate` to `1`. 4. Visit the page from step 2 and confirm that the animation is not-smooth. 5. Visit `about:config` and set `privacy.resistFingerprinting` to `true` 6. Visit the page from step 2 again. ACTUAL RESULTS: Animation is smooth again. EXPECTED RESULTS: Animation should still be not-smooth; or, users should perhaps have a way to make it not-smooth (perhaps some additional preference to let the frame-rate be an allowable fingerprinting target). NOTE: As noted in bug 1863853 comment 7, `resistFingerprinting` isn't really a supported configuration and it's known to reduce usability (in the service of making every user look as similar as possible to websites that might try to measure differences-between-users, which is the point of the pref). However, given that some users use `layout.frame_rate` for a11y purposes, maybe it's worth adding an additional about:config option to let that preference be honored even with `resistFingerprinting` enabled? (Side note for testing this: if you happen to be using Linux with Wayland, you may run into bug 1771017 which makes `layout.frame_rate` have no effect at all. You can avoid that by running `export MOZ_ENABLE_WAYLAND=0` before starting Firefox from your terminal, per bug 1863853 comment 0.)
(This is similar to bug 1863853, but bug is specifically about private-browsing-vs-regular-browsing leakage. This one is more direct.) STR: 1. Start Firefox with a fresh profile. 2. (optional) Visit some page with CSS animations (e.g. [this MDN page](https://developer.mozilla.org/en-US/docs/Web/CSS/animation)) and confirm that the animation is smooth. (Here's another testcase using Flickity which animates on right/leftarrow: https://codepen.io/dholbert/pen/XWwbrRK ) 3. Visit `about:config` and set `layout.frame_rate` to `1`. 4. Visit the page from step 2 and confirm that the animation is not-smooth. 5. Visit `about:config` and set `privacy.resistFingerprinting` to `true` 6. Visit the page from step 2 again. ACTUAL RESULTS: Animation is smooth again. EXPECTED RESULTS: Animation should still be not-smooth; or, users should perhaps have a way to make it not-smooth (perhaps some additional preference to let the frame-rate be an allowable fingerprinting target). NOTE: As noted in bug 1863853 comment 7, `resistFingerprinting` isn't really a supported configuration and it's known to reduce usability (in the service of making every user look as similar as possible to websites that might try to measure differences-between-users, which is the point of the pref). However, given that some users use `layout.frame_rate` for a11y purposes, maybe it's worth adding an additional about:config option to let that preference be honored even with `resistFingerprinting` enabled? (Side note for testing this: if you happen to be using Linux with Wayland, you may run into bug 1771017 which makes `layout.frame_rate` have no effect at all. You can avoid that by running `export MOZ_ENABLE_WAYLAND=0` before starting Firefox from your terminal, per bug 1863853 comment 0.)