Yonke imikhiqizo Isithangami Sokwesekwa

I tried to log in to my Firefox getting started page which used to just load. It now appears to need a log in which I try to do using my Gmail credentials. The password comes up as being incorrect which I know is not the case. If I try to change it I get as far as a Gmail code being sent to my account but when I enter that it says that is incorrect. I have not been able to load the getting started page since.

Hello,

I am trying to force two or three websites to detect my timezone as UTC, even though my local system time is not UTC. I figured out how to do this with ALL sites by setting privacy.fingerprintingProtection to "true" and entering "+JSDateTimeUTC" in privacy.fingerprintingProtection.overrides in about:config.

Now according to docs, privacy.fingerprintingProtection.granularOverrides "can be used to add or remove features on a domain granular level if privacy.fingerprintingProtection is enabled," but I can't figure out how to get it working.

Any input is appreciated.

Windows 11 Pro, Version 10.0.22631 Build 22631 Firefox, 126.0b8 (64-Bit)

Hey,

I use a personal firewall. Every unknown program that attempts to access the network triggers a popup message requesting permission.

Right after the installation, Firefox.exe initiated a message, stating the following path: "C:\Program Files\Mozilla Firefox\firefox.exe". I granted access.

However, weeks after the installation, the updater.exe asked for permission, stating a very unusual path of itself. The path is "\device\harddiskvolume3\Program Files (x86)\Mozilla Maintenance Service\update\updater.exe".

This seems unusual to me, since apps normally use 'C:\' to refer to harddiskdrive0. It is also suspect, since there are only two drives connected and the Disk Management tool (as an admin) indicates, that there are harddiskdrive0 and harddiskdrive1. There are no hard disk drives 2 or 3.

I also wondering about the fact, that the about firefox screen states, that firefox is up to date - even I did not granted access for the updater.exe in the past. There has never been a firwall rule to grant access for the updater.exe - how did it update in the past?

Does anybody have an idea what is happening?

Best regards, André