-
Notifications
You must be signed in to change notification settings - Fork 2
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
Does not support firefox #2
Comments
Currently encountering this bug with Firefox version 111. ##Edit This appears to be an issue with how Mozilla is choosing to implement Manifest V3. Ref: https://stackoverflow.com/questions/75043889/manifest-v3-background-scripts-service-worker-on-firefox Editing the manifest.json file from:
To:
Allowed me to successfully install the addon and it appears to be working correctly. |
I have successfully compiled it and submitted it to Mozilla for signing. After it's been signed, I will post it here so others can just install it right away. |
Were you able to get the extension signed? |
Unfortunately not, Mozilla has been less than lenient with my lack in
extension packing and assuming that I know how that works :D
…--
Moritz Poldrack
https://moritz.sh
|
For those waiting, I was able to get Mozilla's approval. You can download the addon here: https://addons.mozilla.org/addon/briefkasten-unofficial/ |
Describe the bug
When trying to install the extension from Firefox, it gives an error that is is corrupt and so cannot install it. I've ran the following commands:
And then gone to the extension manager => install from file =>
my-extension.zip
From debugging, it seems that it's an invalid manifest version, so I changed that to
2
and then tried it again. Now it gives the following error:Reproduction
View above
System Info
System: OS: Linux 6.0 Pop!_OS 22.04 LTS CPU: (6) x64 Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz Memory: 10.54 GB / 15.56 GB Container: Yes Shell: 5.8.1 - /usr/bin/zsh Binaries: Node: 12.22.9 - /usr/bin/node npm: 8.5.1 - /usr/bin/npm Browsers: Firefox: 107.0
Used Package Manager
npm
Validations
The text was updated successfully, but these errors were encountered: