Previews relies on having an URLRequest in a lot of APIs. It relies on getting the URL as well as storing UserData on the request. The former is easy for s13n, but the latter is a little more complicated. To fully understand this problem, we'd need to understand data_reduction_proxy servicification. Likely, all of the decision making could occur earlier in the navigation lifetime on the UI thread, but coordinating those decisions and getting them to the actual implementors may be more complex.
Comment 1 by bengr@chromium.org
, May 11 2018Status: Available (was: Untriaged)