Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Firefox extensions #12

Open
1 of 4 tasks
zalmoxisus opened this issue Oct 19, 2015 · 5 comments
Open
1 of 4 tasks

Firefox extensions #12

zalmoxisus opened this issue Oct 19, 2015 · 5 comments

Comments

@zalmoxisus
Copy link
Owner

For building Firefox extensions we use WebExtensions's standards, which is still supported only in Firefox Nightly.

To completely support it, we need:

@jhen0409
Copy link
Collaborator

jhen0409 commented Feb 9, 2016

https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox

The Firefox cannot use unsigned extension now, we should recommend use Firefox Developer Edition and disable xpinstall.signatures.required.

Also, the Firefox Developer Edition which can load local directories.

@zalmoxisus
Copy link
Owner Author

@jhen0409, Yes, AFAIK, Firefox doesn't support webextensions at all yet, and we need whether Nightly or Developer Edition.

About signing it is indicated in the load section. I know the readme needs rework :)

The original plan of Mozilla was to migrate to WebExtensions by December last year, but it is taking longer, and for now it is difficult to implement something as the API is too limited.

zalmoxisus added a commit that referenced this issue Feb 11, 2016
@groovecoder
Copy link

Just FYI here, Firefox has implemented a large number of web extensions API since February ...

http://arewewebextensionsyet.com/

@zalmoxisus
Copy link
Owner Author

@groovecoder, thanks for the info. Yes, the API is improving. We did support firefox webextension's api in 'v0.3.1'. Specifically for the current boilerplate we also need chrome.runtime.getBackgroundPage to be supported. Strange that according to that page it is already supported, but according the the issue it's not. I'll look into it.

@groovecoder
Copy link

I used it recently so I'm fairly sure it's supported now. That bug may still be open because of some other chrome.runetime method/property that isn't done yet? 😕

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants