-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Farble navigator.deviceMemory instead of blocking it #12348
Comments
33 tasks
Test plan:
|
Verification passed on
Fingerprinting to "Allow all" - Device Memory
Fingerprinting to "Block (standard)" - Device Memory
Fingerprinting to "Block (strict)" - Device Memory
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we block
navigator.deviceMemory
unconditionally. Instead, proposal:0.5
, return a valid value between0.5
and the true value (see https://developer.mozilla.org/en-US/docs/Web/API/Navigator/deviceMemory for valid values)0.25
, return true valueChoice of value is determined by domain key and session key, as with other farbled values.
The text was updated successfully, but these errors were encountered: