(2013/04/11 4:24), Mihai Sucan wrote:
Hello Joshua!
Le 10/04/2013 20:41, Joshua Cranmer 🐧 a écrit :
On 4/10/2013 12:05 PM, Mihai Sucan wrote:
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].
What are the implications for non-Firefox based projects like Thunderbird and
SeaMonkey?
There should be no implications for non-Firefox based projects. We will not
touch the Error Console, we will only hide
it by default, as explained in the initial email I sent.
Where will the ~650 uses in mozilla-central/comm-central of
Components.utils.reportError report errors to?
Cu.reportError() will continue to work as usual. You will see all of those
errors in the Browser Console.
Best regards,
Mihai
Hi, as TB user, I often find javascript errors in error console when something
does not work right. For example, syntax error (rare, but happens during
testing),
or undefined property error in error console (these are actually rather routine
:-(
I got a few dozen such messages during "make mozmill" test run that gets dumped
in the tty console
where I run DEBUG BUILD of TB.
These happen during the normal operation of thunderbird, UI interaction or
message operation and such,
and without any WEB browsing involved (after all it is TB).
So let me clarify my understanding is correct or not.
These errors issued by JavaScript interpreter will still go to error console,
won't they?
So, if I need to look at them, I touch the about:config to re-enable error
console
to appear on the menu and then click the menu item to see the console for real.
Am I correct in the above understanding?
TIA
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
