I can take this if no one is working on it.

FYI, this issue is the "resource_hints_impl.cc" entry in my list of to-migrate host resolutions:
https://docs.google.com/spreadsheets/d/1Gb6aYHeZ0H1R9-nnOyWGEDFZFaSc_jwllPEBsOQ0KTU

It's currently blocked on support for non-default priority.  I'm actively working on that support right now in https://chromium-review.googlesource.com/c/chromium/src/+/1171574 and another CL for the mojo side.  Hopefully all landed within a couple days.

 Issue 874655  has been merged into this issue.

This probably won't be needed. The only clients of the content::PreresolveUrl() are chrome_browser_net::Predictor and predictors::PreconnectManager.

predictors::PreconnectManager is the replacement for the chrome_browser_net::Predictor and which is already enabled by default.

I'm currently converting predictors::PreconnectManager to use mojo API for the HostResolver. And I think we could leave chrome_browser_net::Predictor unsupported.

So you're saying you're planning on converting predictors::PreconnectManager to directly make host resolution requests rather than going through content::PreresolveUrl()? If so, SGTM as long as content::PreresolveUrl() and chrome_browser_net::Predictor are commented as deprecated.

Removing myself as owner, since it looks like we might not need this.

removing this from blocking 809583 (see comment #6).

Yes, I already have a patch that does this. I've created  Issue 875238  to track chrome_browser_net::Predictor deprecation.

Looks like  Issue 875238  is making progress but still not complete to remove the remaining preresolve usage.  So I'm leaving this bug open, but we likely won't ever have to do anything here except confirm that all preresolves are deleted or migrated to network service.

content::PreresolveUrl() was removed, closing this bug.