Open Bug 1271441 Opened 8 years ago Updated 2 years ago

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

Categories

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

defect

Tracking

()

Tracking Status
firefox49 --- affected

People

(Reporter: bzbarsky, Unassigned)

Details

(Whiteboard: btpp-backlog)

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?
Flags: needinfo?(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.
Flags: needinfo?(ejpbruel)
Boris, can this wait until Eddy has time?
Flags: needinfo?(bzbarsky)
Whiteboard: btpp-followup-2016-05-17
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.
Flags: needinfo?(bzbarsky)
Whiteboard: btpp-followup-2016-05-17 → btpp-backlog
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.