Closed Bug 1271367 Opened 9 years ago Closed 9 years ago

Add ability to disable "about:config"

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 580349

People

(Reporter: yuki, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [design-decision-denied]triaged)

For enterprise use, the system administrator wants users to be restricted to change dangerous secret preferences. MDC ( https://developer.mozilla.org/en-US/docs/MCD,_Mission_Control_Desktop_AKA_AutoConfig ) provides ability to lock preference values by the system administrator, but it is nonsense to lock too many number of preferences. Thus I developed an addon to block loading of "about:config", based on nsIContentPolicy ( https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XPCOM/Reference/Interface/nsIContentPolicy ). After XUL is ended we need something to alter the current method. I've tried to migrate the addon from XUL-based to WebExtensions but it is impossible, because the existing API "chrome.webRequest" (it seems to be an aternative of nsIContentPolicy for the purpose) cannot handle "about:" URIs. Thus I filed the bug 1268370 to allow handling of "about:" URIs for addons, but it has been resolved as WONTFIX from security reason.
Blocks: fx-enterprise
Whiteboard: [design-decision-needed]triaged
How is this different from bug 580349?
Flags: needinfo?(yuki)
The bug 1268370 is focused to an specific method based on chrome.webRequest. On the other hand, this bug is focused to the purpose itself: disabling "about:config" anyway. Thus, "how do it" is not the matter. A new secret preference to do it is a possible solution, if it is best for the purpose. I filed this bug as an WebExtensions issue because I think they are actually an non-dividual topic: addon compatibility problems around ending XUL, and regressions around enterprise use from dying XUL-based addons, and introducing WebExtensions.
Flags: needinfo?(yuki)
We don't plan on this API in WebExtensions. Moving over to Firefox to see if that's something that would happen through configuration of other means.
Component: WebExtensions: Untriaged → General
Product: Toolkit → Firefox
Whiteboard: [design-decision-needed]triaged → [design-decision-denied]triaged
This doesn't belong in webextensions, there is an old bug that should be revived and fixed, duping to that.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.