Julian Descottes [:jdescottes] Reporter
	Description • 7 years ago

The new console frontend is currently explicitly disabled in the browser toolbox and in the browser content toolbox, even if the "webconsole.new-frontend-enabled"
preference is on.

http://searchfox.org/mozilla-central/rev/a5c2b278897272497e14a8481513fee34bbc7e2c/devtools/client/webconsole/webconsole.js#539-541

We need to check if there was a good reason to keep the new console off in those environments, and if not we should probably enable it.

	Julian Descottes [:jdescottes] Reporter
	Comment 1 • 7 years ago

Nicolas, do you know if there is any good reason not to do this?

	Nicolas Chevobbe [:nchevobbe]
	Comment 2 • 7 years ago

If I remember correctly, it was when we decided to enable the new console in nightly, but we weren't at feature parity (and were afraid that there would be still some bugs that would annoy moz people which rely on it). Also, it was a nice way to debug the new console, because if you use it in the browser console too and break it, you can't really see anything :)

Now, I'd say that the console is working pretty well, doesn't lack much in comparison with the old one, so I guess we could enable it in browser toolbox.

Brian may have a different opinion on this, so maybe we could wait until he's back to decide what to do ?

	Tom Tromey :tromey
	Comment 3 • 7 years ago

One way around the debugging issue would be to have a second pref controlling 
which console is used by the browser toolbox.

	Jan Honza Odvarko [:Honza] (always need-info? me)
	Comment 4 • 7 years ago

I think this depends at least on bug 1307895

"LogMessage" log type needs to be supported before we can enable it otherwise there is an exception in convertCachedPacket() function (utils/message.js).

Honza

	Jan Honza Odvarko [:Honza] (always need-info? me)
	Comment 6 • 7 years ago

@Brian, the attached patch requires also patch from bug 1307895

Do you know if there are any other issues blocking us from enabling the new front end in Browser Console/Toolbox?

Honza

	Brian Grinstead [:bgrins] Assignee
	Comment 7 • 7 years ago
mozreview-review

Comment on attachment 8862433 [details]
Bug 1347127 - Enable new console frontend in Browser Toolbox;

https://reviewboard.mozilla.org/r/134366/#review137468

As we discussed, let's wait to merge until we do a pass through remaining bugs and then do a run-through comparison to make sure we aren't either missing features or going to blank out when running in chrome.

::: devtools/client/webconsole/webconsole.js:539
(Diff revision 1)
>     * @private
>     */
>    _initUI: function () {
>      this.document = this.window.document;
>      this.rootElement = this.document.documentElement;
> -    this.NEW_CONSOLE_OUTPUT_ENABLED = !this.isBrowserConsole
> +    this.NEW_CONSOLE_OUTPUT_ENABLED = !this.owner.target.chrome &&

This bug is for the Browser Toolbox but this patch is actually covering the Browser Console path.

I'm not sure if we want to do both in this bug. If so we'd need  to get rid of the `!this.owner.target.chrome` condition as well. If not then we should make a new bug for the browser console.  Let's chat about this next week before making a decision.

	Nicolas Chevobbe [:nchevobbe]
	Comment 8 • 7 years ago

When fixing this bug, we should copy devtools/client/webconsole/test/browser_console_nsiconsolemessage.js to devtools/client/webconsole/new-console-output/test/mochitest/ to ensure everything is working.

	Nicolas Chevobbe [:nchevobbe]
	Comment 10 • 6 years ago
mozreview-review

Comment on attachment 8961432 [details]
Bug 1347127 - Enable new console frontend in Browser Toolbox;

https://reviewboard.mozilla.org/r/230180/#review235822

	Pulsebot
	Comment 11 • 6 years ago

Pushed by bgrinstead@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4ef446fff8e6
Enable new console frontend in Browser Toolbox;r=nchevobbe

	Ryan VanderMeulen [:RyanVM]
	Comment 12 • 6 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/4ef446fff8e6

	Sebastian Zartner [:sebo]
	Comment 13 • 6 years ago

Maybe worth a release note? Not sure how that's requested nowadays, though.

Sebastian

	Brian Grinstead [:bgrins] Assignee
	Comment 14 • 6 years ago

(In reply to Sebastian Zartner [:sebo] from comment #13)
> Maybe worth a release note? Not sure how that's requested nowadays, though.
> 
> Sebastian

I don't think this alone warrants a release note, but this combined with the Browser Console switching (currently on in nightly but will be switched to ride the train in bug 1362023) does. I'll ask for relnote on that bug when we land it.

	Chris Mills [:cmills]
	Comment 15 • 6 years ago

I've added a note to the Fx61 rel notes:

https://developer.mozilla.org/en-US/Firefox/Releases/61#Developer_tools

Does this sound accurate? Of course, there is the bigger task of updating all the screenshots in the devtools documentation to show the new console UI, but I've not got time for this now. I'm going to add this to the long term devtools docs plan.

	Brian Grinstead [:bgrins] Assignee
	Comment 16 • 6 years ago

(In reply to Chris Mills (Mozilla, MDN editor) [:cmills] from comment #15)
> I've added a note to the Fx61 rel notes:
> 
> https://developer.mozilla.org/en-US/Firefox/Releases/61#Developer_tools
> 
> Does this sound accurate? Of course, there is the bigger task of updating
> all the screenshots in the devtools documentation to show the new console
> UI, but I've not got time for this now. I'm going to add this to the long
> term devtools docs plan.

Thanks! Instead of "The new-look Web/Browser Console UI has been enabled by default" I might say something like "The new Web Console UI has been enabled in the Browser Toolbox and Browser Console" to clarify that this isn't a change to the normal devtools toolbox (where the new UI has been enabled for a few releases already).