Open Bug 1593753 Opened 2 years ago Updated 7 months ago

Remove the "Browser Content Toolbox"

Categories

(DevTools :: General, task, P3)

Product:
DevTools
Component:
General
Type:
task

Tracking

(Not tracked)

People

(Reporter: ochameau, Unassigned)

References

(Depends on 1 open bug, Blocks 3 open bugs)

Details

As the Omniscient Browser Toolbox progress, the Browser Content Toolbox becomes useless.
This toolbox is the one you open from "Web Developer" Menu and "Browser Content Toolbox" entry.
It opens a special toolbox, with just the console, debugger and memory, which are debugging the content process into which the current tab is running.

The Omniscient Browser Toolbox allows to debug the parent process and all the content processes, all at the same time, in a unique Toolbox. This makes the Browser Content Toolbox irrelevant and unecessary limited.

Priority: -- → P3
Duplicate of this bug: 1603376
Blocks: dt-fission

Before removing the Browser Content Toolbox, we probably should:

  • enable the JS Context selector by default in the Browser Toolbox (bug 1628346), so that we can still evaluate JS in the content processes,
  • enable the Multiprocess Browser Toolbox on all channels (bug 1625937), so that everyone can debug all processes, on all channels.
Depends on: 1628346, 1625937

(In reply to Alexandre Poirot [:ochameau] from comment #2)

Before removing the Browser Content Toolbox, we probably should:

  • enable the JS Context selector by default in the Browser Toolbox (bug 1628346), so that we can still evaluate JS in the content processes,
  • enable the Multiprocess Browser Toolbox on all channels (bug 1625937), so that everyone can debug all processes, on all channels.

Bug #1 has been fixed already.

Blocks: 1672614
You need to log in before you can comment on or make changes to this bug.