Add an interface to allow consumers to subscribe/unsubscribe to network change events, and convert content/'s and chrome/'s net::NetworkChangeNotifier (NCN) consumers to using it.
There are some cleanup needed in Issue 754695 to make NCN observer interface cleaner.
One cause of weirdness here is that the NCN is a singleton. Ideally, that would mean you can just create an NCN subclass that acts as a proxy for the NCN in the network service, but NetworkService is also being run in process currently, to help with migration (And on Android, the network service will always run in process). Anyhow, sounds like you're not planning on going down that path, anyways, just thought I'd point out that option ends up being weirder than one might think.
Comment 1 by xunji...@chromium.org
, Aug 11 2017