We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
from.example -> a.click.example/bounce -> a.click.example/dest
bc /bounce and /dest share the origin.
However, this chain would be debounced:
from.example -> a.click.example/bounce -> b.click.example/dest
The correct behavior is for neither of the above redirect chains to be debounced
The text was updated successfully, but these errors were encountered:
Labelled as QA/No after discussing the above with @pes10k and @pilgrim-brave via the Slack thread that @LaurenWags started.
QA/No
Sorry, something went wrong.
1.46.x - Release
pilgrim-brave
Successfully merging a pull request may close this issue.
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: