>>2564532You've piqued my autism, since I've made extensions in the past:
1. What version of Firefox are you using? I'm using 88.
2. Could you link to a page which produces that error? If it is all pages, just provide one at random.
3. Are you trying to run it in a private window/tab?
If that all results in nothing, I can take a look at the errors you get if you want. Can understand if that's a bit much:
1. Enter "about:debugging" into the URL bar
2. Go to "This Firefox"
3. Scroll down to that Copyfish, click "Inspect," go to "Console"
4. Move that debugging tab to a new window for easier viewing
5. Attempt to use Copyfish again
6. See what console output comes up, red being errors/exceptions. While it shouldn't be leaking anything personal, you can just stick to what pops up when it runs and fails and review that for info that isn't just the extension trying to run. Pic related.
>Thought it was interference from another addon so disabled everything except copyfish but it still happens.Probably not the case unless you are running an addon that operates with something outside of individual web pages. Ever since Firefox moved to WebExtension years ago, addons are sandboxed by default and have no access to other addons unless the devs build in pre-established messages to listen for. Doesn't mean one addon can't tell another to do something, but the receiving addon has to be designed to listen for that message and do its work independently of the other addon:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/runtime/sendMessage>I also have Capture2Text which is usable anywhere so that's pretty good.Ah, good to hear.
