I'd try Tampermonkey first just to see. Switching browsers sounds more annoying to me, but I suppose depending upon how many scripts you have, that may be more of an undertaking that I'm thinking.
I do get some very rare problems with addons, though. I have to stop and start them. In some order I've not figured out yet but after a few tries it works.
It might be this thing again. I'll look into it later. At any rate, thanks for helping narrow it down. Otherwise, I've have had to test with different browsers, userscript managers, and also try a bunch of userscripts in case it was related to specific ones.
@Makyen Violentmonkey Firefox userscript issues: Workaround: in Violentmonkey's "Advanced" settings, check "Synchronous page mode" checkbox. Known fix: downgrade to the prior version and disable Violentmonkey updates in about:addons. More detail: The recently-updated, current version of Violentmonkey, 2.13.5, has issues with loading userscripts in page mode, which is how most userscripts need to be loaded, due to how most userscripts' are written. The workaround of checking the "Synchronous page mode" checkbox resolved the issues in limited testing, but more testing is needed to be sure that's really sufficient. It is known that downgrading your copy of Violentmonkey to the prior version, 2.12.13, will solve the issue. The most recent older version, 2.12.13, can be downloaded from here for Firefox. You can see all released versions of Violentmonkey for Firefox on addons.mozilla.org. If you downgrade, you will probably want to disable automatic updates for Violentmonkey from Violentmonkey's extension configuration page which you can access from about:addons. [This has been edited to remove an inaccurate explanation and to provide the workaround that doesn't require downgrading.]
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
Potential workaround for Violentmonkey issue with the most recent version (needs more testing): In Violentmonkey's "Advanced" settings: Check the "Synchronous page mode" option. This appeared to resolve the issues in the limited testing I did with a limited number of userscripts. Setting that option is probably less disruptive than downgrading and disabling updates.
You may want/need to set "Default injection mode" to "page". Most userscripts are designed to work in "page" mode and many will break if injected in "content" mode.
