I changed fp_navigator and fp_useragent to test with the correct version.
The screen dimensions test was failing because letterboxing is disabled on about:pages (I checked with Richard, and this is the intended behavior). Therefore, the test is now run after loading the a TPO page, and it passes.
As a result of these settings changes, some DOM objects are now exposed:
- pointer events
visualViewportHowever, Tor Browser already contains mitigations against their use for fingerprinting (e.g., gamepads do not work, Mozilla added some protections to pointer events, letterboxing should prevent fingerprinting on
visualViewport, cache storage is 0 bytes, etc...). Some other DOM objects are just new (e.g.,
Finally, the HTTPS everywhere test failed because now Firefox redirects to HTTPS if available, even when HTTPS-Only Mode is not enabled.
To detect if HTTPS everywhere is actually the responsible of the redirect, we need to run it with
dom.security.https_first_pbm set to