-
Notifications
You must be signed in to change notification settings - Fork 6
Use content script to get selection and become a pure WebExtension #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Yes, if you could fix the tests, that would be great. |
The scripting.messageDisplay API was introduced in ESR 128
Somehow not all exceptions are catched. When the message area is hidden (F8) and the export button is pressed, the following exceptions are thrown: Traceback
Do you have an idea why the exception doesn't get catched? |
Interesting. You are triggering the message action from a browser action button, which could therefore act on a tab, which does not have a message. Does a check if we actually display a message fix this for you? A consequence of this is, that you have no button in a message displayed in a window. You either have to specifically request that via the manifest entry |
Yes, that works.
That would be a good addition. I will check that on a separate branch. Thanks for your efforts! |
With the introduction of the new Thunderbird Release channel, updating Experiment add-ons every 4 weeks will become very time-consuming. We therefore doubled our effort to identify add-ons, which could be converted to pure WebExtensions.
As it turned out, this add-on is one of them: It uses an Experiment to get the currently selected text. This PR replace the Experiment by a content script.