Open
Bug 1345983
Opened 8 years ago
Updated 3 years ago
Add an option to hide the Debugger
Categories
(DevTools :: Framework, enhancement)
Tracking
(Not tracked)
REOPENED
People
(Reporter: sebo, Unassigned)
References
(Blocks 1 open bug)
Details
There should be a way to disable and hide the Debugger within the Settings panel like it's available for other tools.
Sebastian
Updated•8 years ago
|
Component: Developer Tools: Debugger → Developer Tools: Framework
Reporter | ||
Comment 1•8 years ago
|
||
Does this actually require more than hiding the tab from the tab bar? If not, it may be a 'good-first-bug'.
Sebastian
Flags: needinfo?(ntim.bugs)
Comment 2•8 years ago
|
||
This is easy to do, but this depends on whether UX agrees with this change or not.
Also, I think it is a bit more than hiding the tab from the tab bar. You need to handle the "Open in Debugger" links across the toolbox.
Flags: needinfo?(ntim.bugs)
Comment 3•8 years ago
|
||
I'm going to close this for now.
If you disable everything you can in the options panel, you end up with Inspector, Console and Debugger. Which we consider is the bare minimum, and what people will be expecting.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Comment 4•8 years ago
|
||
I came across some websites that prevent you from using DevTools properly by putting a "debugger;" statement in their code, and running the code periodically. Is there a bug filed about preventing that use-case ?
Flags: needinfo?(pbrosset)
Reporter | ||
Comment 5•8 years ago
|
||
(In reply to Patrick Brosset <:pbro> from comment #3)
> I'm going to close this for now.
> If you disable everything you can in the options panel, you end up with
> Inspector, Console and Debugger. Which we consider is the bare minimum, and
> what people will be expecting.
You should keep in mind that some users of the DevTools are designers or analysts, which may have no need for the debugger.
(In reply to Tim Nguyen :ntim from comment #4)
> I came across some websites that prevent you from using DevTools properly by
> putting a "debugger;" statement in their code, and running the code
> periodically. Is there a bug filed about preventing that use-case ?
I filed bug 1300934 for this and similar use cases and came up with the idea to allow to handle them like breakpoints in https://github.com/devtools-html/debugger.html/issues/828, so they can be disabled.
Sebastian
Flags: needinfo?(pbrosset)
Updated•7 years ago
|
Product: Firefox → DevTools
Reporter | ||
Comment 6•7 years ago
|
||
(In reply to Sebastian Zartner [:sebo] from comment #5)
> (In reply to Patrick Brosset <:pbro> from comment #3)
> > I'm going to close this for now.
> > If you disable everything you can in the options panel, you end up with
> > Inspector, Console and Debugger. Which we consider is the bare minimum, and
> > what people will be expecting.
>
> You should keep in mind that some users of the DevTools are designers or
> analysts, which may have no need for the debugger.
Due to the focus on web design tools lately, I think it's clearer than ever that some users of the DevTools do not use the JavaScript debugging features. Therefore I reopened this issue. Patrick, please let me know if you think different.
Sebastian
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•