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

Visiting .user.js URL on a domain that doesn't exist makes TM for Chrome go bonkers #2278

Open
JasonBarnabe opened this issue Dec 4, 2024 · 1 comment

Comments

@JasonBarnabe
Copy link

With Tampermonkey for Chrome, visit https://thisdoesnot.exist/test.user.js

Expected Behavior

Just a normal Chrome error page.

Actual Behavior

Tampermonkey's "intermediate step" keeps opening and closing forever.

Specifications

  • Chrome 131.0.6778.85
  • TM 5.3.2
  • Ubuntu 24.04.01
@derjanb
Copy link
Member

derjanb commented Dec 5, 2024

Yeah. I have to think about how to fix this. Tampermonkey detects that there is no script, blocks script detection and hands the URL over to Chrome, and unblocks script detection. Then after some (short) time Chrome retries to load the URL (like it does with all/many error pages) and Tampermonkey intercepts the request again. And in theory this is right, because on every Chrome-triggered reload a script could possibly appear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants