-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fix stats leakage #86
Conversation
@philipp-classen @smalluban please review commits in isolation and do not squash on merge. |
75025e9
to
33664aa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked at the commits separately, and they look fine. However, my knowledge about the ghostery common is very limited (and how the webrequest pipeline works), so I cannot say much more.
}, | ||
} | ||
}; | ||
if (!global.crypto) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it is currently written (after the PR), the tests have the side effects to change
global.crypto === undefined
(before tests) to global.crypto !== undefined
(after tests)
8e3681d
to
79e74d7
Compare
79e74d7
to
e2f148f
Compare
closing in favor of smaller PRs |
PR aims to prevent adblocker and anti-tracking stats "leaking" between navigations. Sadly the solution is not complete for Ghostery use-case as the same problem is also present in the Ghostery codebase.