Closed Bug 1371762 Opened 6 years ago Closed 6 years ago

Legacy page shows an experiment


(Toolkit :: Add-ons Manager, defect, P3)




Tracking Status
firefox56 --- fixed


(Reporter: andy+bugzilla, Assigned: aswan)



(Whiteboard: investigating)


(2 files)

On Nightly

1. install a legacy extension
2. install a webextensions experiment
3. turn on the legacy extension pref
4. note that the webextensions experiment appears in the legacy page

This will never happen in release, so prioritize accordingly.

This will only occur if you have at least one legacy extension.
To be clear, step 3 actually means legacy extensions should be disabled right?

I think I might be missing something but experiments are bootstrapped addons so if they are not signed with "Mozilla Extensions" and legacy extensions are disabled, this sounds like everything is working as intended.
Flags: needinfo?(amckay)
But from what I can tell, it hasn't been disabled.
Flags: needinfo?(amckay)
the experiment not being disabled is surprising.  why not and does this impact something else.
Flags: needinfo?(aswan)
Priority: -- → P3
Whiteboard: investigating
Assignee: nobody → aswan
Flags: needinfo?(aswan)
Blocks: 1336576
Attachment #8878696 - Flags: review?(rhelmer)
Attachment #8887996 - Flags: review?(rhelmer)
Comment on attachment 8878696 [details]
Bug 1371762 Part 1 Let cert shim code selectively identify some xpis as privileged
Attachment #8878696 - Flags: review?(rhelmer) → review+
Comment on attachment 8887996 [details]
Bug 1371762 Part 2 Treat webextension experiments as legacy
Attachment #8887996 - Flags: review?(rhelmer) → review+
Pushed by
Part 1 Let cert shim code selectively identify some xpis as privileged r=rhelmer
Part 2 Treat webextension experiments as legacy r=rhelmer
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in before you can comment on or make changes to this bug.