Sahbi Posted September 30, 2024 Posted September 30, 2024 Simply having the extension loaded already causes it to inject a content script to intercept the browser's native function calls, which happens even if the extension is locked. Can we make this functionality entirely optional? It conflicts with other plugins trying to do the same, so I'd actually classify this as a bug (but I'm not even sure where to report those).
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now