This is not for the developer of the page to solve. While biking back home, a possible cause popped up in my mind: could one of the add-ons I use cause this and yes, that appears to be the case. I restarted with disabled add-ons and the message was gone. Then I enabled them one … Read more
Firefox dev tools network inspector still truncates responses to 1MB by default. You can change or disable the limit by navigating to about:config and changing devtools.netmonitor.responseBodyLimit. To disable the limit, set it to 0.
We changed the Firefox setting (about:config) ‘network.http.max-persistent-connections-per-server’ to 64 and the blocks went away. We changed it back to 6. We changed our design/development method to a more ‘asynchronous’ loading method so as not to have a large number simultaneous connections. The blocks were mostly loading a lot of png flags for locale settings.
Firefox’s native developer tools have come a long way since this question was written. The differences have mainly reduced to the following points: Can’t stop the script execution on DOM mutations, XHRs, or cookie changes. XPaths can’t be copied. Missing an events side panel in the Inspector (though events are displayed within the DOM structure). … Read more
As of June 2020, there is no official method/way of achieving http request requester filtering/identification. Currently the only possibility is what is done on the question’s code which is separating requests from web-pages/tabs and the other Firefox’s components (feed updates, extensions requests, XHR requests from XPCOM components, etc). As mentioned on the comments this is … Read more
Open Firefox Developer Tools Click anywhere within Firefox Developer Tools Press Ctrl++ on Unix/Win or Cmd++ on Mac To be clear, I mean the + key. You don’t need to hold the Shift key while doing it.
From Firefox 31 onwards you can use the “Enable persistent logs” setting to prevent the Network Monitor from clearing the list on reload.