The task is similar to crbug/702318. There is a difficulty of plumbing the meta data of tasks across all layers.

This task will be put on hold until the TaskType is available in TaskQueueManager.

Which method are you referring to? In general the TQM already knows about task queues, in particular task types.

Talked off-line with npm@. By task-type, it means the one defined as generic-task-sources -
 https://html.spec.whatwg.org/multipage/webappapis.html#generic-task-sources. It's not in TQM et. Thanks anyway:)

Never mind, wrong tasktype

Shubhie, as far as I can tell, there's no consensus on the spec end of things that this would be the task type we want to expose.

Does it make sense for us to dig into this before we're confident of how the spec will shape up? I suppose the dance around layering constraints will be pretty similar, but it might just make sense to wait for now.

Seems like we should be able to add the most obvious one today: "networking" task source (this is both in spec and scheduler)
But fine to wait as we don't know the rest of the task types yet.

We haven't been able to prioritize sorting out the spec issues here yet.

Next step is coming up with a concrete proposal for task types, and running it by the working group.

Filed issue on the spec repo here:
https://github.com/w3c/longtasks/issues/40

Ping myself as it's getting stale.

Not prioritized the task yet. Pinged the w3c issue.

Ping from bug triage: Any update on this? 

Updates from on w3c:

https://github.com/w3c/longtasks/issues/40#issuecomment-389557834

blocking on spec