Open Bug 1674764 Opened 4 years ago Updated 3 years ago

Lazy fetching of Network requests flow through the Resource API

Categories

(DevTools :: Netmonitor, task, P3)

Product:
DevTools
Component:
Netmonitor
Type:
task

Tracking

(Fission Milestone:Future)

Project Flags:
Fission Milestone Future

People

(Reporter: bomsy, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: dt-fission-future)

Since the resource watcher exists, lets investigate if the lazy loaded requests data can flow through the Resource API or at least modify/contribute to the NETWORK_EVENT cached object. So that redux stored object is always the same as the NETWORK_EVENT resource.

Blocks: network-panel-infra
Severity: -- → S3
Priority: -- → P3
Whiteboard: dt-fission-m3-mvp

Tracking dt-fission-m3-mvp bugs for Fission MVP.

Fission Milestone: --- → MVP
Whiteboard: dt-fission-m3-mvp → dt-fission-m3-reserve

Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.

Fission Milestone: MVP → Future
Whiteboard: dt-fission-m3-reserve → dt-fission-future
You need to log in before you can comment on or make changes to this bug.