SupervisedUserResourceThrottle interposes on main frame network requests to block requests for certain URLs. We're working towards wrapping the network stack in a Mojo interface, and it would be good to minimize or eliminate Chrome code that's behind that Mojo boundary. Since this class only cares about navigations, we can hook it up as NavigationThrottle, and have it live on the UI thread. As an added bonus, the new code will require less setup, since it has to get data from the UI thread anyways during construction.
Comment 1 by mmenke@chromium.org
, Mar 27 2017