ui.prefersReducedMotion

[wvxwxvw]

Twice in a document with different values. First it is enabled, and then, according to the instructions for non-RFP users, it is disabled.

[Thorin-Oakenpants]

Correct. It's disabled added as part of RFP because that comes before the one in RFP alts: it makes no sense to put it in the 5000's, inactive, and ask users to add it as an override: so it's enabled active and does not affect fingerprinting (due to RFP)

But if a user decides to disable RFP and instead they turn on the RFP Alts section, then the second value is applied last, and the fingerprinting is still covered

how a user.js works

It parses the user.js in the order it is written, i.e if the same preference is listed twice with two different values, the last one will be applied last

[rusty-snake]

/* 4520: disable chrome animations [FF77+] [RESTART]

Where is the FPing/Security?

[Thorin-Oakenpants]

Are you asking how PRM is fingerprintable (it is), or why it's included when all the other prefs not in 5000s have some sort of privacy/security/anti-tracking/anti-FPing aspect and this one doesn't?

[rusty-snake]

I'm wondering why we need to disable animations for firefox. There is no security issue and I don't see the FPing (as long as RFP is used).

[Thorin-Oakenpants]

Because Mozilla tied a chrome setting to a web setting

The pref is already covered by RFP, but if we enforce it as 1 (which leaks with no RFP) then no-one will need to add it as an override to disable the megabar etc, which means anyone who then needs to flip on RFP Alts is not compromised (because the value 1 is set before the alt value 0 is set: so Alts wins)

capisce?

[crssi]

@Thorin-Oakenpants Is there anything you have not think of at all? 😄 ❤️

[Thorin-Oakenpants]

@Thorin-Oakenpants Is there anything you have not think of at all? 😄 ❤️

I forgot my mom's birthday once .. she's never let me live it down ... 47 years and counting .. *sigh*