<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello everyone!<br>
<br>
Yesterday we landed a couple of changes for the Web Console [1] and
we also included the new Browser Console, <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=587757">bug
587757</a>. [2] To try it please set <var>devtools.chrome.enabled</var>
to <code>true</code> in <a class="moz-txt-link-freetext"
href="about:config">about:config</a>. Then you can go to the <b>Web
Developer > Browser Console</b> menu item. If you use nightly
builds, you may have to wait for tomorrow's builds.<br>
<br>
The Browser Console displays all of the network requests happening
in the browser, along with all of the script and style
errors/warnings. All of the <var>window.console</var> API messages
are also included. This tool no longer filters messages based on
window IDs, so you get things from the Firefox chrome, from addons
and from open tabs - much like the Error Console.<br>
<br>
The Web Console will continue to remain tab specific - it will
always filter messages relevant to the tab it is open for. When you
find a message that is relevant to a web page in tab that doesn't
show in the Web Console please file a bug report.<br>
<br>
The developer tools team would like to:<br>
<ol>
<li>by default hide the Error Console menu item from the Web
Developer menu and put that behind the <var>devtools.errorconsole.enabled</var>
pref.</li>
<li>enable the Browser Console by default, such that tech-savvy
users of Firefox can be directed to the Browser Console to
copy/paste any debug information we need. See <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=798925">bug
798925</a> [3] for the rationale - why the Error Console was
enabled by default.</li>
<li>change the current Error Console keyboard shortcuts to open
the Browser Console instead.<br>
</li>
</ol>
The developer tools team had planned for a long time to replace the
Error Console with a better tool, as you can see from bug 587757.<br>
<br>
The rationale is simple: our goal is to constantly improve and make
it easier to debug the browser and the addons users and developers
have installed in Firefox.<br>
<br>
We plan to make further improvements to the Browser Console. Given
it shares the same code with the Web Console expect a lot of changes
as we move ahead. Things you can expect:<br>
<ol>
<li>you will be able to use the console API from JSMs:<br>
<br>
<code>let console = Cu.import(<a class="moz-txt-link-rfc2396E"
href="resource://gre/modules/devtools/Console.jsm">"resource://gre/modules/devtools/Console.jsm"</a>,
{}).console;</code><code><br>
</code><code>console.log("foobar", omgObject);</code><br>
<br>
... the above will show in the Browser Console. This will work
from any browser or addon code. See <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=851231">bug
851231</a>. [4]<br>
</li>
<li>we hope we can eliminate the need to do <code>Cu.import()</code>
for Console.jsm, so you can directly use the |console| object in
any jsm, without imports. See <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=851695">bug
851695</a>. [5]<br>
</li>
<li>improved output: better UI and UX, stack traces for errors and
console API calls, and more. See <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=778766">bug
778766</a>. [6]<br>
</li>
<li>improved autocomplete.<br>
</li>
</ol>
<br>
Please test the Browser Console and file bugs as you find them.
Current known issue is <a
href="https://bugzilla.mozilla.org/show_bug.cgi?id=859756">bug
859756</a> [7], which I will fix ASAP.<br>
<br>
If anyone has any concerns about us replacing the Error Console,
please shout loud and clear! We plan to do the aforementioned steps
to replace the Error Console in the current release cycle, maybe in
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=602006">bug
602006</a> [8].<br>
<br>
Thank you very much!<br>
<br>
<br>
[1]
<a class="moz-txt-link-freetext"
href="http://www.robodesign.ro/mihai/blog/web-console-improvements-and-the-new-browser-console">http://www.robodesign.ro/mihai/blog/web-console-improvements-and-the-new-browser-console</a><br>
[2] <a class="moz-txt-link-freetext"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=587757">https://bugzilla.mozilla.org/show_bug.cgi?id=587757</a><br>
[3] <a class="moz-txt-link-freetext"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=798925">https://bugzilla.mozilla.org/show_bug.cgi?id=798925</a><br>
[4] <a class="moz-txt-link-freetext"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=851231">https://bugzilla.mozilla.org/show_bug.cgi?id=851231</a><br>
[5] <a class="moz-txt-link-freetext"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=851695">https://bugzilla.mozilla.org/show_bug.cgi?id=851695</a><br>
[6] <a class="moz-txt-link-freetext"
href="https://bugzilla.mozilla.org/show_bug.cgi?id=778766">https://bugzilla.mozilla.org/show_bug.cgi?id=778766</a><br>
[7] <a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=859756">https://bugzilla.mozilla.org/show_bug.cgi?id=859756</a><br>
[8] <a class="moz-txt-link-freetext" href="https://bugzilla.mozilla.org/show_bug.cgi?id=602006">https://bugzilla.mozilla.org/show_bug.cgi?id=602006</a><br>
<br>
</body>
</html>