Hello everyone!
Yesterday we landed a couple of changes for the Web Console [1] and we
also included the new Browser Console, bug 587757
<https://bugzilla.mozilla.org/show_bug.cgi?id=587757>. [2] To try it
please set devtools.chrome.enabled to |true| in about:config. Then you
can go to the *Web Developer > Browser Console* menu item. If you use
nightly builds, you may have to wait for tomorrow's builds.
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 window.console 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.
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.
The developer tools team would like to:
1. by default hide the Error Console menu item from the Web Developer
menu and put that behind the devtools.errorconsole.enabled pref.
2. 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 bug 798925
<https://bugzilla.mozilla.org/show_bug.cgi?id=798925> [3] for the
rationale - why the Error Console was enabled by default.
3. change the current Error Console keyboard shortcuts to open the
Browser Console instead.
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.
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.
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:
1. you will be able to use the console API from JSMs:
|let console =
Cu.import("resource://gre/modules/devtools/Console.jsm", {}).console;||
||console.log("foobar", omgObject);|
... the above will show in the Browser Console. This will work from
any browser or addon code. See bug 851231
<https://bugzilla.mozilla.org/show_bug.cgi?id=851231>. [4]
2. we hope we can eliminate the need to do |Cu.import()| for
Console.jsm, so you can directly use the |console| object in any
jsm, without imports. See bug 851695
<https://bugzilla.mozilla.org/show_bug.cgi?id=851695>. [5]
3. improved output: better UI and UX, stack traces for errors and
console API calls, and more. See bug 778766
<https://bugzilla.mozilla.org/show_bug.cgi?id=778766>. [6]
4. improved autocomplete.
Please test the Browser Console and file bugs as you find them. Current
known issue is bug 859756
<https://bugzilla.mozilla.org/show_bug.cgi?id=859756> [7], which I will
fix ASAP.
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 bug 602006
<https://bugzilla.mozilla.org/show_bug.cgi?id=602006> [8].
Thank you very much!
[1]
http://www.robodesign.ro/mihai/blog/web-console-improvements-and-the-new-browser-console
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=587757
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=798925
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=851231
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=851695
[6] https://bugzilla.mozilla.org/show_bug.cgi?id=778766
[7] https://bugzilla.mozilla.org/show_bug.cgi?id=859756
[8] https://bugzilla.mozilla.org/show_bug.cgi?id=602006
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
