Skip to content
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

Google link tracking redirect removal is broken in Incognito in MV3 #3062

Open
ghostwords opened this issue Feb 19, 2025 · 0 comments
Open
Labels
bug Chrome first-party relating to first-party scripts MV3 Manifest V3-specific issue

Comments

@ghostwords
Copy link
Member

ghostwords commented Feb 19, 2025

The main problem in MV3 with our Google link tracking redirect removal workaround (8a637bc) for w3c/webextensions#302 is that it doesn't work in Incognito, even if Privacy Badger is enabled to run in Incognito.

This page has been blocked by Chrome
ERR_BLOCKED_BY_CLIENT

The secondary problem with the workaround is that you can briefly see a redirect to a chrome-extension:// page. This feels bad/slow/confusing to users.

@ghostwords ghostwords added bug Chrome first-party relating to first-party scripts MV3 Manifest V3-specific issue labels Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Chrome first-party relating to first-party scripts MV3 Manifest V3-specific issue
Projects
None yet
Development

No branches or pull requests

1 participant