@ -24,7 +24,8 @@ For the same reason as the last question. That's how the `@match` directives are
- ~~Figure out why it doesn't work on Firefox~~
- ~~It's because the `@run-at context-menu` header only works in Chrome based browsers. The context menu item *appears* in Firefox but doesn't do anything. Find a workaraound~~
- It's actually because of something extremely different and much, much weirder. `@run-at context-menu` actually does exist in Firefox now, but there's a bizarre CSP enforcement bug that causes Firefox issues. Details on the installation page
- ~~It's actually because of something extremely different and much, much weirder. `@run-at context-menu` actually does exist in Firefox now, but there's a bizarre CSP enforcement bug that causes Firefox issues. Details on the installation page~~
- Fixed in an update to Tampermonkey
- ~~Don't rely on parsing human-readable text, won't work in other languages~~
- There's no good API or anything for this, going to need to parse the document structure
<p>Ensure Tampermonkey is installed: <ahref="https://www.tampermonkey.net/">Tampermonkey Home Page</a><ahref="https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo">Chrome Extension</a><ahref="https://addons.mozilla.org/en-US/firefox/addon/tampermonkey/">Firefox Add-On</a></p>
<p><aid="firefoxnote-link"href="#firefoxnote"><strong>Extremely important note for Firefox users! Read this or the script WILL NOT WORK!</strong></a></p></div>
<p>Ensure Tampermonkey is installed: <ahref="https://www.tampermonkey.net/">Tampermonkey Home Page</a><ahref="https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo">Chrome Extension</a><ahref="https://addons.mozilla.org/en-US/firefox/addon/tampermonkey/">Firefox Add-On</a></p></div>
<hr>
@ -72,7 +70,9 @@
<hr>
<divid="firefoxnote"><h2>Note For Firefox Users</h2>
<divid="firefoxnote"><h2><s>Note For Firefox Users</s></h2>
<h3>This script used to be broken in Firefox, and this part of the page details a workaround. A Tampermonkey update has fixed the bug, so this is no longer required unless you're on an old version of Tampermonkey for some reason.</s></h3>
<p>There's currently an extremely weird bug somewhere in the intersection of Tampermonkey and Firefox. I've managed to find a few reports of it occuring for other people, but only in the context of other issues that have since been closed. I have no idea what causes it, but there is a workaround.</p>
Holly