Closed
Bug 863814
Opened 12 years ago
Closed 12 years ago
Add the console API to web and chrome workers
Categories
(DevTools :: Console, defect, P2)
DevTools
Console
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 620935
People
(Reporter: msucan, Unassigned)
Details
Web and Chrome workers cannot use the window.console API. There's no good reason why we do not allow that.
I imagine we need cannot use the dom/base/ConsoleAPI.js implementation as it is for web workers.
However, I wonder how we can add new objects and APIs to web workers and if web workers can know their owning window inner ID. If the answer is yes, we can definitely add a console API implementation for workers.
Boris: can you please point us to what we should do? Thanks!
Comment 1•12 years ago
|
||
> I wonder how we can add new objects and APIs to web workers
Either by defining a WebIDL interface for them (and a C++ implementation) or "very painfully" (as in, raw JSAPI), as far as I know.... Ben or Kyle might know more.
It should certainly be possible to pass the window id to non-shared workers, and we don't do shared workers yet.
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #1)
> > I wonder how we can add new objects and APIs to web workers
>
> Either by defining a WebIDL interface for them (and a C++ implementation) or
> "very painfully" (as in, raw JSAPI), as far as I know.... Ben or Kyle might
> know more.
Are there any such examples in the codebase? I'd like to see how painful that is.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•12 years ago
|
||
Heh, search fail on my part. Thanks Masatoshi.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•