It’s fine. I have signing turned off cause I am also a extension developer. Here are some things I found.
Script does not load on certain websites (github and this website) giving an error:
Error: Error: Script returned non-structured-clonable data
If you spam the browser action button, it creates many of those scripts. So you would have to click the X on each one of them (minor bug)
It would be nice to have the extension to have an active mode where it translates the current website. So that on a page navigation on that website, I don’t have to click the browser action each time. (Use case: Visit a foreign news website -> translate page -> click on an article I like to read -> article is already translated)
Though it seems like you are using Google Translate’s remote external script, which I don’t know how much control they would give you in implementing 3.
Although if I’m not mistaken, AMO does not allow remote execution of scripts. So you would have to package Google Translate’s scripts in your extension, but ask a reviewer to make sure.
So I can test my extension normally in my main browser and fix stuff as needed without adding an extra step of signing my extension and not being able to use that version number anymore.
CSP also affects local requests. I don’t think I can go around it without doing something really hacky. I think addons should not respect CSP rules since they have their own permission system.
Not sure about the remote code thing. I will execute remote code from the web site that I asked permissions from. It will not be in a priviledged context. I will see how that can work out. https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Reviews