Migrate all methods of NetworkEventActor to NetworkContentActor
Categories
(DevTools :: Netmonitor, task, P3)
Tracking
(Fission Milestone:Future)
Fission Milestone | Future |
People
(Reporter: ochameau, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-fission-future)
For now, we moved only one method from NetworkEventActor to NetworkContentActor: getStackTrace
, but we should move all of them in order to stop using DevToolsClient.request
/WebConsoleFront
for these requests:
https://searchfox.org/mozilla-central/rev/dac45cc7020dfddbcc937827810dd11550c07dc3/devtools/client/netmonitor/src/connector/firefox-data-provider.js#531-547
Here is the methods we should expose via NetworkContentActor
:
https://searchfox.org/mozilla-central/rev/dac45cc7020dfddbcc937827810dd11550c07dc3/devtools/server/actors/network-monitor/network-event-actor.js#145-260
We may keep these methods on NetworkEventActor, but the ultimate goal, alongside bug 1687237 will be to make NetworkEventActor become just an helper class on the server, and no longer be an actor. This will still be used by NetworkEventWatcher
and keyed by resourceId
. But we will drop the notion of actor and front which is hard to maintain.
Comment 1•4 years ago
|
||
Adding into the M3 reserve list, so it isn't forgotten when we are planning a follow up Clean-up sprint.
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Tracking dt-fission-m3-reserve bugs for Fission M8 (blocking Release channel experiment, but not Beta experiment).
Comment 3•4 years ago
|
||
Moving "dt-fission-m3-reserve" bugs to "dt-fission-future" because they don't block Fission MVP.
Description
•