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

Support Web Extension Experiments workflows in this template #53

Closed
motin opened this issue Feb 27, 2018 · 6 comments · Fixed by #73
Closed

Support Web Extension Experiments workflows in this template #53

motin opened this issue Feb 27, 2018 · 6 comments · Fixed by #73

Comments

@motin
Copy link
Contributor

motin commented Feb 27, 2018

The template has been sporting a hybrid legacy add-on / web extension workflow for quite a while now, but it still requires messaging between the web extension and legacy add-on code to workaround the limitations of the web extension apis. A first step is to remove the need for this messaging and instead craft web extension apis to remove need for legacy code for common study operations.

This should take is one step further away from legacy add-ons and towards a full web-extension-based workflow as described in mozilla/shield-studies-addon-utils#45

@motin
Copy link
Contributor Author

motin commented Feb 27, 2018

Current efforts:

@motin
Copy link
Contributor Author

motin commented Feb 27, 2018

@motin
Copy link
Contributor Author

motin commented Feb 28, 2018

@motin
Copy link
Contributor Author

motin commented Mar 1, 2018

@biancadanforth
Copy link
Collaborator

Just as an update: I have not yet had the opportunity to work on a study that takes the form of a WEE, which is how I was going to make the template. Please see the README for examples in the meantime until the official template is built.

@motin
Copy link
Contributor Author

motin commented Jun 3, 2018

Update: The develop-branch of this template is now a study add-on with a bundled Web Extension Experiment, using the latest release candidate of Shield Utils v5

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

Successfully merging a pull request may close this issue.

2 participants