Closed Bug 1596961 Opened 3 months ago Closed 3 months ago

Fix an inaccuracy in the experiments doc about running unsigned extensions

Categories

(Firefox :: Address Bar, enhancement, P3)

enhancement
Points:
2

Tracking

()

RESOLVED FIXED
Firefox 72
Iteration:
72.3 - Nov 18 - Dec 1
Tracking Status
firefox72 --- fixed

People

(Reporter: adw, Assigned: adw)

Details

Attachments

(1 file)

As I'm testing the nudges extension, I'm referencing the doc and the section about running an unsigned extension normally (not temporarily) isn't quite right. It's right when it comes to loading the extension, but it's wrong in that the extension is not able to access privileged APIs. There doesn't seem to be a way to let unsigned non-temporary extensions access privileged APIs without modifying the isPrivileged getter.

I also spent like five minutes wondering why the extension's logs weren't showing. The section talks about it but only at the very bottom, and it's easy to overlook. I think it still belongs after the main discussion, but I made it an important note so it stands out.

As I'm testing the nudges extension, I'm referencing the doc and the section about running an unsigned extension normally (not temporarily) isn't quite right. It's right when it comes to loading the extension, but it's wrong in that the extension is not able to access privileged APIs. There doesn't seem to be a way to let unsigned non-temporary extensions access privileged APIs without modifying the isPrivileged getter.

I also spent like five minutes wondering why the extension's logs weren't showing. The section talks about it but only at the very bottom, and it's easy to overlook. I think it still belongs after the main discussion, but I made it an important note so it stands out.

Pushed by dwillcoxon@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/67de1c204ffb
Fix an inaccuracy in the experiments doc about running unsigned extensions r=harry
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
You need to log in before you can comment on or make changes to this bug.