Fix delay caused by network api

[alxclark]

There seems to be some delay in the dev tools when the webpage connects but somehow the dev tools disconnects itself and it takes a while for it to be ready and receive/send a connection event to the content-script. This should be instant every time since the dev tools panel does not change and is persisted through page refresh.

Looks like the network api is the culprit here, during a page reload, the dev tools panel has to process dozens/hundreds of network requests while also trying to execute the onConnect even for each page reload that attempted to connect to the dev tools. The amount of requests induces a large delay before the dev tools panel can process the next onConnect listener.

So how do we fix this ?

• requestIdleCallback
  • Not very reliable, sometimes the browser will offload for a very long time if the webpage is very active. This gives very poor UX.
• Debounced getHAR
  • HAR always return what is in the network tab
  • Con: It respects the preserve log option from the network tab which could differ from the persistence setting in aside. There could be a layer on top of the api to filter out requests made before the page load. After initial load, it would be costly to re-query the full HAR and filter it again. It also respects the recording state in the network tab, so it could come out empty.

[alxclark]

For now, it hasn't been solved, but the network feature is behind the network capability which reduces the green path when using aside without network integrated.