Closed Bug 1339676 Opened 4 years ago Closed 7 months ago

Label runnables in netwerk/


(Core :: Networking, defect, P3)




Tracking Status
firefox54 --- affected


(Reporter: kershaw, Assigned: kershaw)



(Keywords: stale-bug, Whiteboard: [necko-triaged])

Meta bug for labeling all runnables in necko.
Whiteboard: [necko-next]
Hi Bevis,

I would like to make sure that my understanding about labeling on IPC actors is right.
Do we have to label all IPC actors under PNecko like what we did for HttpChannelChild in bug 1318506?
If yes, there are 15 actors [1] needed to be labeled. Is there a more efficient way instead of labeling them one by one?


Flags: needinfo?(btseng)
Per offline discussion,
there is no efficient way in this case, because these actors are at the same managee level, and we can't inherit the event target from their manager unless they are expected to be the same in your design.
BTW, if some of these actors are not touched by the content and the order of the callback won't be an impact to other docgroups, then you can just label them in SystemGroup.
Flags: needinfo?(btseng)
Depends on: 1343741
Depends on: 1343743
Summary: Labeling runnables in netwerk/ → Label runnables in netwerk/
Depends on: 1343745
Depends on: 1343747
Depends on: 1343750
Depends on: 1343755
Depends on: 1343761
Whiteboard: [necko-next] → [necko-next][QDL][TDC-MVP][NECKO]
Whiteboard: [necko-next][QDL][TDC-MVP][NECKO] → [necko-next]
Depends on: 1355688
Whiteboard: [necko-next] → [necko-active]
Depends on: 1377544
Depends on: 1378484
Depends on: 1378489
Depends on: 1384294
Depends on: 1388247
Bulk priority update:
Priority: -- → P1
Is this targeted for 57 or will we punt to 58?
Flags: needinfo?(kechang)
Whiteboard: [necko-active]
(In reply to Jason Duell [:jduell] (needinfo me) from comment #4)
> Is this targeted for 57 or will we punt to 58?

This should be targeted for 57.

Only bug 1388247 is left to 58.
Flags: needinfo?(kechang)
Whiteboard: [necko-triaged]
Priority: P1 → P3

Close since labeling project is done.

Closed: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.