-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
Current efforts:
|
Related (available in 59): Bug 1323845 - Allow bundled experiments, and support for content-side APIs |
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. |
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 |
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
The text was updated successfully, but these errors were encountered: