Closed Bug 1813108 Opened 2 years ago Closed 2 years ago

Figure out extension pinning

Categories

(Firefox :: Enterprise Policies, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
113 Branch
Tracking Status
firefox113 --- fixed

People

(Reporter: mkaply, Assigned: mkaply)

References

Details

Attachments

(1 file, 1 obsolete file)

We need to either add the ability to pin individual extensions to the toolbar via policy (which Chrome has in ExtensionSettings) or allow setting the default value to toolbar versus the new extension menu.

We should just follow the Chrome ExtensionSettings to allow pinning.

Assignee: nobody → mozilla
Status: NEW → ASSIGNED
Severity: -- → N/A
Priority: -- → P3
Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/c24f7a077e5f Add support for pinning to ExtensionSettings policy. r=willdurand

Backed out changeset c24f7a077e5f (Bug 1813108) for mochitest failures on test_ext_action.html.
Backout link
Push with failures <--> 4
Failure Log
Also gv-junit-nifis Failure Log

Flags: needinfo?(mozilla)
Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/cb3c9ccc76d6 Add support for pinning to ExtensionSettings policy. r=willdurand
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
Flags: needinfo?(mozilla)
Duplicate of this bug: 1741226
Attached file ESR patch (obsolete) —

Comment on attachment 9328611 [details]
ESR patch

I'm not going to put this in the ESR. while Chrome has always had the policy, it's really only interesting after 109.

Attachment #9328611 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: