Hash sign as a path component in a user script's @match command prevents the script from running
I try to exactly match a login page in a website, for a user script manager (USM) script, which I run with Tampermonkey.
This pattern didn't work:
// @match https://example.com/#/login
This pattern worked:
// @match https://example.com/*
Why would the Hash sign (#) prevent the script from running?
By "prevent the script from running" I mean that Tampermonkey (version 4.13) just won't start the script on that webpage if the first pattern is used.
1 answer
The part after the hashtag is called a URI fragment. Unfortunately, Tampermonkey does not allow you to match hashtags.
This is arguably for good reason. The hashtag can easily change (and for single page applications, often does easily change) without a page reload. Since userscript managers load their scripts when the page loads, they simply can't match based on the URI fragment.
Therefore, you will have to check for the fragment in your script's code. It shouldn't be more difficult than just checking location.hash
0 comment threads
1 comment thread