Update Safari's navigational-tracking mitigations. #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 18, 2022
jyasskin
force-pushed
the
update-safari-mitigations
branch
from
94136e6
to
d3b1cc5
Compare
johnwilander
approved these changes
May 24, 2022
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #19. @johnwilander, please check that I've accurately described the subset of https://webkit.org/tracking-prevention/ that you'd count as navigational tracking mitigations. I removed the 7-day restriction on client-written storage since I think it's not done in response to any indication of navigational tracking, but I could keep it if you think it's part of this effort.
Preview | Diff