1271441 - Need to fix console reporting and whatnot in the worker error reporter

Status: NEW

(Core :: DOM: Workers, enhancement, P3)

Description

[Boris Zbarsky [:bzbarsky]]

It's a total mess.  I'm adding some comments in bug 1268845, but basically it can end up firing error events on the worker for things the debugger is doing and so forth.  :(

Eddy, do you have time to try to make this stuff better?

Comment 1

[Eddy Bruel [:ejpbruel]]

(In reply to Boris Zbarsky [:bz] from comment #0)
> It's a total mess.  I'm adding some comments in bug 1268845, but basically
> it can end up firing error events on the worker for things the debugger is
> doing and so forth.  :(
> 
> Eddy, do you have time to try to make this stuff better?

Not at the moment, no. Our focus for this quarter is the devtools.html process. We're also using a new development process in where we're not really supposed to work on things that aren't already in the backlog.

I have several other worker related issues that I'd like to look into, so I'm hoping I'll be able to put this back on our radar for Q3.

Comment 2

[Andrew Overholt [:overholt]]

Boris, can this wait until Eddy has time?

Comment 3

[Boris Zbarsky [:bzbarsky]]

Yeah.  It means no error reporting on malformed JSON when importing bogus JWK keys on a worker, and some weirdness if we trigger an overrecursion error in the debugger on a worker, but we can live with those for a bit.

I might just do it myself too; I can't estimate when yet.

Comment 4

[Andrew Sutherland [:asuth] (he/him)]

The comments bz added in bug 1268845 still exist, just migrated to WorkerError.cpp.