user_pref(“”, 900) // ī) just maximize after starting, it’s one click * The override values are a starting point to round from if you want some control * Width will round down to multiples of 200s and height to 100s, to fit your screen. * 4502: set new window sizes to round to hundreds So RFP applies a sizing on NEW windows.Ī) Use the prefs to create a larger window on open That said, RFP doesn’t stop you resizing a window, it ONLY controls NEW windows (so it has issues when you change the chrome: manual resizing, going full screen, maximizing, toggle menubar, toolbar, sidebar, changing density, even changing themes (if they affect paddings and margins of some chrome elements). It would be more productive and responsible to explain why this is necessary, the risks, and possible workarounds (of which there are several). And it covers LOTS of stuff, so disabling because of one thing isn’t a valid reason. So you don’t get to pick and choose which parts of it you want. But the point is, RFP is an all-in buy-in, so that way everyone has the same FP.
It’s not perfect and still has a long way to go: e.g fonts and web audio FP’ing still isn’t covered: and that’s just items that simple common scripts like fpjs2 use.
privacy.resistFingerprinting (RFP) protects against an awful lot of metrics that can be used in fingerprinting. I’d just like to say that this is terrible advice.
