877389 - (remove-cu-reportError) [meta] Replace calls to Cu.reportError, etc. from browser code, replace with console.error, etc.

Status: NEW

(Firefox :: General, defect, P3)

Description

[Rob Campbell [:rc] (:robcee)]

No reason to cling to the past. Let's make things pretty!

Comment 1

[Alex Lakatos[:AlexLakatos]]

If you list all the calls you meant by "etc.", I'll take this on.

Comment 2

[Rob Campbell [:rc] (:robcee)]

Cu/Components.utils.reportError()
Services.console.logStringMessage()
...logMessage()

I bet there are a bunch more but this should get you started.

Comment 3

[Dave Townsend [:mossop]]

We probably need bug 851695 for this, maybe also something to add console.jsm to JS component scopes

Comment 4

[:Gavin Sharp [email: [e-mail]]]

What's the benefit? Don't Cu.reportError calls already show up in the browser console?

Comment 5

[Justin Dolske [:Dolske]]

I think I spawned this on Twitter, but I what I was really asking for is for a better replacement for nsIConsoleMessage. Right now JS is basically limited to logging a simple string, and you have to mess with this old (and often unscriptable) XPCOM goop to do something like log a warning instead of an error.

It would be super awesome if this was well integrated with a log4moz replacement (or dare I dream of better nspr logging?).

Comment 6

[Mark Banner (:standard8)]

Turning this into a meta as we're going to start migrating across.