Right now the console API in content processes ends up reporting messages to the content processes' console service, which doesn't reach the parent process/UI in any way. We could either: - have console.log in content processes use the message manager, and arrange to not have a console service in the child processes - have the console service handle sending all messages to the parent

I was wrong about the console service being involved - console.* messages are sent directly to the UI observers via the observer service, and so the solution needed here is console.*-specific. (Bill pointed out that ContentChild already has a ConsoleListener that forwards messages to the parent.)

I'm rewriting the Console API in C++ unifying the different implementations we have. If you have needs about how to fix issue for e10s, let me know.

(In reply to Andrea Marchesini (:baku) from comment #2) > I'm rewriting the Console API in C++ unifying the different implementations > we have. This is happening in bug 965860.

Thanks Andrea. The rewrite seemed to have fixed this. I just tested, and console.log works as far as I can see. It looks like the message gets passed up through the remote debug protocol.