This assumes that networking is running in the same process, which isn't the case with the network service.
For notifications about frame requests, WebContentsObserver::DidFinishNavigation is a substitute. r515725 did this for SafeBrowsingNavigationObserver.
ClientSideDetectionHost is the remaining user. It gets notifications for both frame request and subresources. For the latter, we would have to start plumbing this data from the renderer to the browser, to be compatible with the mode where network runs in a separate process.
Then we can remove WebContentsObserver::DidGetResourceResponseStart altogether.
Blocking this on bug 783977 because we have no integration tests for ClientSideDetectionHost.
Comment 1 by jam@chromium.org
, Nov 21 2017Status: Started (was: Available)