Open Bug 1247198 Opened 8 years ago Updated 2 years ago

Unable to disable Debugger or Inspector tools

Categories

(DevTools :: Framework, defect, P4)

46 Branch
defect

Tracking

(Not tracked)

People

(Reporter: Hoffmann.P, Unassigned)

Details

(Whiteboard: [btpp-dbm])

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/48.0.2564.82 Chrome/48.0.2564.82 Safari/537.36

Steps to reproduce:

1. opened about:config
2. searched for devtools.debugger.enabled
3. switched to "false"
4. restarted



Actual results:

I pressed F12 to open the devtools and switched to the debugger-tab.
It still shows


Expected results:

either the tab dissappears, it can't be opend or is empty
Also don't work:
devtools.inspector.enabled = false
Component: Untriaged → Developer Tools
This is currently expected, as some tools are considered "core" tools that are deeply integrated with each other.  This is why the Toolbox Options pane (gear icon) doesn't have checkboxes for these tools.

In any case, we can use this bug to discuss if that still makes sense.
Status: UNCONFIRMED → NEW
Component: Developer Tools → Developer Tools: Framework
Ever confirmed: true
Summary: "devtools.debugger.enabled: false" does not work → Unable to disable Debugger or Inspector tools
We are using a modified kiosk-mode Firefox for testing kids (or their teachers ;-) in school and would like to disable any distraction from the tests. (distraction, not cheating, we know that there is a plethora of ways to cheat). If disabling should not be possible, removing these options would be great!
(and possibly a way to remove the develop bar from the UI?)
(In reply to Hoffmann.P from comment #3)
> We are using a modified kiosk-mode Firefox for testing kids (or their
> teachers ;-) in school and would like to disable any distraction from the
> tests. (distraction, not cheating, we know that there is a plethora of ways
> to cheat). If disabling should not be possible, removing these options would
> be great!
> (and possibly a way to remove the develop bar from the UI?)

Does this mean you are build Firefox from a source tree?  Or just customizing with prefs and add-ons?
Until now, we tried to archive our target without building and just customizing
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #2)
> This is currently expected, as some tools are considered "core" tools that
> are deeply integrated with each other.  This is why the Toolbox Options pane
> (gear icon) doesn't have checkboxes for these tools.
> 
> In any case, we can use this bug to discuss if that still makes sense.

Are you wanting to disable the Developer Tools entirely?  Or specifically trying to hide the Inspector and Debugger panels from the Developer Tools toolbox?
Flags: needinfo?(Hoffmann.P)
(In reply to Hoffmann.P from comment #3)
> We are using a modified kiosk-mode Firefox for testing kids (or their
> teachers ;-) in school and would like to disable any distraction from the
> tests. (distraction, not cheating, we know that there is a plethora of ways
> to cheat). If disabling should not be possible, removing these options would
> be great!
> (and possibly a way to remove the develop bar from the UI?)

Write a style to userChrome.css may be able to as workaround for now.
Filter on TEAPOT-SPLINES.

More information needed from the reporter about what exactly they need.
Priority: -- → P4
Whiteboard: [btpp-dbm]
We would like to have a way to configure the browser so that all devtools can be disabled. We tried to archive that by disabling every single component which didn't work hence the bug report.
Wie fixed the problem by hiding the components using the userChrome.css style sheet.
Flags: needinfo?(Hoffmann.P)
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.