Chrome + JShelter 0.20.2 on the antifingerprinting test page that Brave created is not spoofing anything. When you check this website https://dev-pages.brave.software/fingerprinting/farbling.html Everything comes out the same with or without JShelter enabled (default settings). Also tried to enable Chrome Extensions Developer Mode, that did not make any difference.
Pages affected: https://dev-pages.brave.software/fingerprinting/farbling.html JShelter Version: 0.20.2
Popup information (open JShelter popup on affected pages:
Modify
Detail tweaks of JS shield for this site
OS: Windows 11 Browser: 135.0.7049.116 Other extensions that might affect JShelter behaviour: None, as I tried on a fresh Chrome profile.
Have different fingerprinting values as when doing it without JShelter extension enabled
Same values, nothing detected.
Hello @shepherd,
can you clarify what exactly do you mean by "Everything comes out the same with or without JShelter enabled (default settings)." and also clarify the how to reproduce section that does not match the expected result. Specifically, your how to reproduce steps does not include enabling or disabling JShelter.
I tried several tests on my own.
First of all, let us try Brave (1.78.94 - Chromium 136) without JShelter:
Now let us try Chromium 136 with JShelter active but disable JS Shield for the test domain:
Let us disable JShelter in chrome://extensions and close the tab with the test. Open new one to be sure that JShelter is gone:
Let us reenable JShelter in chrome://extensions and close the tab with the test to be sure that JShelter is later properly loaded:
Go back to global JShelter settings and reenable FPD:
Summary on Chromium:
Additional note:
Metadata Update from @polcak: - Issue tagged with: design decision, question, research