So, `GOOGLE_US_URL` and `GOOGLE_XX_URL` are used by Mozilla for search attribution - which is why we've been clearing them
But it looks like Mozilla also uses `GOOGLE_URL` for the purpose of determining the URL to replace with the `GOOGLE_US_URL` and `GOOGLE_XX_URL` (depending on the region)
So while I'm unable to reproduce the crash in that issue (I suspect it's region-specific), I suspect it's related to this feature; Fenix might be trying to replace the Google URL with nothing... hence it panics
If this still doesn't resolve the issue, we can also try setting the values of `GOOGLE_US_URL` and `GOOGLE_XX_URL` to match the values of `GOOGLE_URL`
Signed-off-by: celenity <celenity@celenity.dev>
This should allow for easier maintenance and updates in the future, and provides all of our custom settings in one centralized place (This is also similar to ex. LibreWolf)
Signed-off-by: celenity <celenity@celenity.dev>
Since we no longer have to worry about this being fingerprintable, we can add a UI toggle, similar to Chromium, so that users can easily use a different PDF viewer if preferred
Signed-off-by: celenity <celenity@celenity.dev>
This is especially important since we now have uBlock Origin as optional on the onboarding; and even with that aside, this is also beneficial for other reasons - ex. I suspect that this will improve performance, this will ensure users are still protected if they disable uBo for a site, etc... - In general, I also just think this is better handled by the browser
Signed-off-by: celenity <celenity@celenity.dev>
While we currently block WebGL by default with uBlock Origin (and it's similarly possible to block WebRTC with uBlock Origin), these toggles are useful for users who want to disable WebGL and/or WebRTC globally, and know they don't need/wish to use it for ANY website. This is also primarily beneficial from a security perspective, as it also provides further attack surface reduction
Signed-off-by: celenity <celenity@celenity.dev>
We can use these to cover important information for the time-being, until the website is ready - once it is, we'll move content from here to there
Signed-off-by: celenity <celenity@celenity.dev>
This also sets the browser theme back to the default of automatic/following the device's theme, since the website appearance is what's actually fingerprintable
Signed-off-by: celenity <celenity@celenity.dev>
This is probably the last aggressive setting that we inherited from Mull, known to cause a significant amount of breakage on sites - now that we have UI toggles for it, we can set it back to the saner default (This is also the default for ex. LibreWolf, Tor Browser, etc)
So we've now officially eliminated nearly all notable breakage out of the box, which I think is great - I feel like we've been working towards this for a while now :)
Signed-off-by: celenity <celenity@celenity.dev>
