Fission should fix this.

Yulia, can you just confirm if the Fission protocol work fixes this; or if there is more work needed?

I haven't looked very much into this so I might not be the best person to ask. but we have had work done with service workers to allow target switching, and the bug is still there. Maybe Brian Hackett knows more? He has been working on this.

console.log(this) in a worker now produces '[object DedicatedWorkerGlobalScope]', though I don't know what fixed this.

(In reply to Brian Hackett (:bhackett) from comment #5)

console.log(this) in a worker now produces '[object DedicatedWorkerGlobalScope]', though I don't know what fixed this.

Oops, I didn't read this bug closely enough, the behavior here is still the same as in comment 0.

The problem here is that when the console tries to encode the global used in the worker for sending to the ConsoleAPIStorage service in the main thread (from which the worker console messages will be retrieved), that encoding fails and we fall back to converting the object to a string. The relevant code is in ConsoleRunnable::CustomWriteHandler() in dom/console/Console.cpp; the UNWRAP_OBJECT() macro produces a NS_ERROR_XPC_BAD_CONVERT_JS error.

Brian, would bug 1252945 help with this?

(In reply to :Harald Kirschner :digitarald from comment #8)

Brian, would bug 1252945 help with this?

I think it would be better to look at this again once the related fission work for a multithreaded console is done, as Nicolas refers to in comment 21 of that bug. When console messages do not need to be dispatched from the worker thread to the main thread, it will be a lot easier to show those messages in the console without losing information.

Thanks Brian for clarifying.

Nicolas, could you please mark the right bug as a dependency.