Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

force dark theme through resistFingerprinting #48

Closed
alexmo1997 opened this issue Jan 4, 2022 · 3 comments
Closed

force dark theme through resistFingerprinting #48

alexmo1997 opened this issue Jan 4, 2022 · 3 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@alexmo1997
Copy link

I really like using the firefox pref privacy.resistFingerprinting, which enhances privacy a lot, but also blocks ui.systemUsesDarkTheme and browserSettings.overrideContentColorScheme.

I'd like to make an exception in this case though, as browsing with a dark theme is more important to me than one bit of information for possible trackers.

This used to be possible with this extension in its v1 architecture (which did some js tricks I guess), but obviously doesn't work anymore as of the use of overrideContentColorScheme.

So it would be awesome if there was a way to enable the old method of setting the color-scheme, so you could force prefers-color-scheme: dark and still have privacy.resistFingerprinting with its bunch of other features.

@alexmo1997 alexmo1997 added the enhancement New feature or request label Jan 4, 2022
@rugk
Copy link
Owner

rugk commented Jan 4, 2022

Duplicate of #22

@rugk rugk marked this as a duplicate of #22 Jan 4, 2022
@rugk rugk closed this as completed Jan 4, 2022
@rugk rugk added the duplicate This issue or pull request already exists label Jan 4, 2022
@rugk
Copy link
Owner

rugk commented Jan 4, 2022

Hi and thanks for your report. This is actually a known issue.
So please have a look here. The TL;DR is: You can use the old v1 extension version if you are in need of that feature. Unfortunately, as you correctly said, with the new API that is not currently possible, and is a limitation of Firefox we cannot influence.
However, I am also reluctant to include the old code there, not only because of the technical complexity, also because it generally was an ugly hack/workaround, I'd not like to go back.

So the currently suggested workaround is, unfortunately, to install a v1 version of the extension and disable auto-updates. There is not much I can do here, I'm afraid.

Also notice that the v1 way may be detectable by websites, i.e. websites may be able to detect that you are using this extension, although we did everything to prevent this, it cannot be 100%ly eliminated. So privacy-wise, this is also a double-edged sword.

@alexmo1997
Copy link
Author

Oh, somehow I couldn't find that with the GitHub search.

Well, that's unfortunate.
I can understand why you don't wanna include the old hack though, thanks for the consideration anyway. I'm gonna use v1 for now then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants