Closed jreidgreer closed 7 years ago
Identified. This is an unfortunate affect of trackers redirecting to each other, not injected assets as I believed. Chrome separates out network calls even if they redirect. the webRequest.onCompleted
event, however, only cares about the end result. The event pipeline for calls will need to be enhanced, but this doesn't have a high level of difficulty.
Network calls initiated by other assets in the page (such as a
google-analytics.com/analytics.js
file), behave inconsistently but most often do not appear in traceable network activity. It's possible the network activity is being observed but simply not assigned to the proper tab.