-
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
Same-site debouncing restriction should be based on eTLD+1 #25859
Labels
Milestone
Comments
25 tasks
pilgrim-brave
added
QA/Yes
release-notes/include
OS/Android
Fixes related to Android browser functionality
OS/Desktop
labels
Nov 29, 2022
Labelled as |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently we don't debounce a link if two hops in the chain have the same origin. This should be expanded to be eTLD+1 matches, not just origin.
For example, currently this chain is not debounced in Brave:
bc /bounce and /dest share the origin.
However, this chain would be debounced:
The correct behavior is for neither of the above redirect chains to be debounced
The text was updated successfully, but these errors were encountered: