Skip to content
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

Switch to Web Extensions #41

Open
nt1m opened this issue Aug 22, 2015 · 3 comments
Open

Switch to Web Extensions #41

nt1m opened this issue Aug 22, 2015 · 3 comments

Comments

@nt1m
Copy link
Owner

nt1m commented Aug 22, 2015

See https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ .

Here are the main obstacles :

  • DevTools Editor component doesn't work with unprivileged code (that's the main reason I switched from a Jetpack add-on to a privileged chrome add-on)
  • Same for theme-switching script
  • Lack of a DevTools add-on API with Web Extensions (there is one for jetpack though)
  • No synced storage support yet for Web Extensions
@nt1m
Copy link
Owner Author

nt1m commented Aug 22, 2015

Since the add-on is already using HTML for it's UI and not abusing of XPCOM, the switch will be pretty easy once the obstacles are cleared.

@yfdyh000
Copy link

yfdyh000 commented Nov 9, 2017

Any news?

@nt1m nt1m changed the title Switch to Web Extensions/Jetpack Switch to Web Extensions Nov 9, 2017
@nt1m
Copy link
Owner Author

nt1m commented Nov 9, 2017

@yfdyh000 I had a WIP that simply adds a simple devtools panel: https://github.com/nt1m/devtools-prototyper/tree/webextension

This add-on is lower priority than VivaldiFox, so it might not get attention right away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants