[Bug] Setting the wrong user @match prevents opening the menu

[esperecyan]

If the incorrect syntax “user@match” is set, then the Greasemonkey menu will not open at all.

It is still possible to recover from this situation, as Greasemonkey menus can still be opened in about:addons and so on.

Error: @match: Invalid host specified. MatchPattern.js:81:11

greasemonkey/third-party/MatchPattern.js

Lines 80 to 82 in 11e340b

	if (!REG_HOST.test(host)) {
	throw new Error("@match: Invalid host specified.");
	}

[arantius]

Confirmed. This comes from inside monkey-menu.js in the loadScripts() function, when checking whether the script runs on the current page.

[arantius]

For a bit more detail: This bug comes through

greasemonkey/src/browser/monkey-menu.js

Line 331 in 11e340b

function loadScripts(userScriptsDetail, url) {

calling

greasemonkey/src/user-script-obj.js

Line 149 in 11e340b

runsOn(url) {

on each script, which relies on

greasemonkey/src/user-script-obj.js

Line 173 in 11e340b

_testCludes(url) {

.

If this last helper, _testCludes() finds a match from includes, excludes, or any match before the invalid user match nothing happens. (This is effectively the workaround, except that comes from runsOn() and causes it to never call the helper at all.) If none of these cases occur, we get to the bottom of _testCludes() which involves attempting to parse the (user) match string into a match object, which previously failed and was uncaught. Any invalid user match, not just the literal user@match will trigger this failure, if the code gets this far.

[arantius]

I've checked with the above commit that adding a bad match in the script editor still gives an error, and installing a script with a bad match (e.g. https://gist.github.com/arantius/d8fadc5affd40fa5acdff34925189965 ) still gives an error, as desired in both cases.

[arantius]

This should be done. I could use your help testing this! Checkout or download Greasemonkey's source code, then follow the documentation for installing an extension during development. As far as I know this will break installed scripts, so you should use about:profiles to create and launch a new blank Firefox profile to do so, rather than overwriting your existing Greasemonkey install. (Maybe take a Greasemonkey backup first to be safe.)

Any testing results, positive or negative, would be great.

[esperecyan]

Thanks for the fix!　I was able to confirm that can open the menu with the incorrect user @match by testing the following steps.

1. In Greasemonkey 4.11, adds https://*example.com/* to user @match.
2. Confirmed that the menu no longer opens.
3. Installs 8bd283f.
4. Confirmed that can open the menu and can remove incorrect @match.