Lin Clark [:linclark] Reporter
	Description • 8 years ago

This META collects blockers to turning on the web console in Developer Edition. This does not include browser console or browser toolbox.

	Patrick Brosset <:pbro>
	Comment 1 • 8 years ago

There's been some discussion about the HTTP inspector lately and whether or not it should actually block this bug.

It has been added not long ago to the old console front-end (in version 48, in bug 1211525 I believe), in particular to help Firebug people migrate over to devtools.

If we don't implement this in the new console before it rides the train, then people using it today may miss it when the new version gets to them.

3 solutions:

- we add it to this bug and don't ride the trains before it's implemented,
- we don't add it here and do it later (possibly uplifting it if necessary),
- we don't add it here, and don't implement it at all, favoring the current workflow which is: click on a network request in the console output takes you to the netmonitor (which does have an HTTP inspector).

This needs to be a product decision. Pinging Bryan on this account.

	Bryan Clark (DevTools PM) [:clarkbw]
	Comment 2 • 8 years ago

On the whole we need a better macro perspective for our tools.  The user stories related to debugging network issues or network timing issues should lead us to the correct approach which is much harder to see at an individual (panel) micro level.

(In reply to Patrick Brosset <:pbro> from comment #1)
> There's been some discussion about the HTTP inspector lately and whether or
> not it should actually block this bug.
> 
> It has been added not long ago to the old console front-end (in version 48,
> in bug 1211525 I believe), in particular to help Firebug people migrate over
> to devtools.
> 
> If we don't implement this in the new console before it rides the train,
> then people using it today may miss it when the new version gets to them.

We don't have any direct metrics for usage of this feature AFAIK.  Let this be a lesson to us all. :-(

> 3 solutions:
> 
> - we add it to this bug and don't ride the trains before it's implemented,
> - we don't add it here and do it later (possibly uplifting it if necessary),

Lets start with this approach.  With this uplifting to DevEdition we'll see usage from another set of users who use the console quite a bit.  Gathering feedback from those users will give us some sense about the need to uplift this in November.

> - we don't add it here, and don't implement it at all, favoring the current
> workflow which is: click on a network request in the console output takes
> you to the netmonitor (which does have an HTTP inspector).

The major concern with this approach is that we believe Nightly and DevEdition users to be more proficient with the tools, which might mean that this feature is more appealing to the larger beta and release audiences where it will be too late to uplift by the time we land there and get feedback.

	Brian Grinstead [:bgrins]
	Comment 3 • 7 years ago

The new console frontend is now active on all channels for the web toolbox, so resolving this one