Closed Bug 1778559 Opened 3 years ago Closed 3 months ago

Consider just disabling the "load temporary addon" button when addon installation is disabled

Categories

(Firefox :: Enterprise Policies, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
140 Branch
Tracking Status
firefox140 --- fixed

People

(Reporter: mkaply, Assigned: mkaply)

Details

Attachments

(1 file)

Currently we block about:debugging if addons are blocked so that temporary addons can't be loaded.

about:debugging can be useful, we should just disable the button.

Severity: -- → N/A
Priority: -- → P3
Assignee: nobody → mozilla
Status: NEW → ASSIGNED

Bumping this to see what can be done - I was surprised that blocking extensions except those allowed also blocked remote debugging. (https://firefox-source-docs.mozilla.org/devtools-user/about_colon_debugging/index.html). Now I cannot debug websites loaded in Firefox for Android from my Firefox desktop.

On Chrome, the DevTools is still allowed regardless of Extension policies (and could open DevTools on an enabled webextension as well.

Thanks for the push on this one. Should be straightforward.

Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/567608985d9c Just disable addon button if policy forbids extension installation. r=devtools-reviewers,jdescottes
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
QA Whiteboard: [qa-triage-done-c141/b140]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: