Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox reports incorrect timezone despite privacy.resistFingerprinting being false

  • No replies
  • 1 has this problem
  • 27 views
sophie1889
sophie1889
more options

Hi,

Firefox reports an incorrect timezone (UTC), despite `privacy.resistFingerprinting` being false. (None of the settings underneath `privacy` have been changed.

The clearest example is here: https://browserspy.dk/date.php (screenshot attached). Another browser (epiphany) reports the correct timezone on that page.

I have tested the following versions: - Mozilla Firefox 102.11.0esr - Mozilla Firefox 113.0 - Mozilla Firefox 113.0b9

It persists under `--safe-mode`, in Private Browsing mode and despite being signed into a firefox account or not.

uname -a: Linux s 6.3.4 #1-NixOS SMP PREEMPT_DYNAMIC Wed May 24 16:30:25 UTC 2023 x86_64 GNU/Linux

timedatectl, displays correct timezone

I'm at a loss at how to proceed and debug this, every search leads back to privacy.resistFingerprinting, but as mentioned this isn't the case here.

Hi, Firefox reports an incorrect timezone (UTC), despite `privacy.resistFingerprinting` being false. (None of the settings underneath `privacy` have been changed. The clearest example is here: https://browserspy.dk/date.php (screenshot attached). Another browser (epiphany) reports the correct timezone on that page. I have tested the following versions: - Mozilla Firefox 102.11.0esr - Mozilla Firefox 113.0 - Mozilla Firefox 113.0b9 It persists under `--safe-mode`, in Private Browsing mode and despite being signed into a firefox account or not. uname -a: Linux s 6.3.4 #1-NixOS SMP PREEMPT_DYNAMIC Wed May 24 16:30:25 UTC 2023 x86_64 GNU/Linux timedatectl, displays correct timezone I'm at a loss at how to proceed and debug this, every search leads back to privacy.resistFingerprinting, but as mentioned this isn't the case here.
Attached screenshots