Initial support will be for Chrome OS only; support for this API on Windows or other platforms is limited at best.

So, I did some investigation, and networkingPrivate.onNetworkListChanged should work just fine for this case.

* This will always get fired if the default (active) network changes, or if the connection state of the default network changes.
* The default network is always the first network in the list.
* This will also get fired when there is no change to the default (active) network, but only in response to a user action such as showing the networking UI (which initiates a scan).

Is there any reason that will not suffice?

Based on what I found in comment #3 and a lack of response I am closing this as WontFix. Feel free to re-open if you think we do need it.

What's described in #3 is somewhat different from what's requested in #1, since it also fires in response to network scans, which we don't want.

Agreed that it is somewhat different, but given that network scans are only performed in response to a user action (login, resume from sleep, or opening a UI element) is that really an important distinction?

I don't believe that's true, so yes, it's an important distinction.

You don't believe what is true? I have recently verified on a Pixel 2 that networkingPrivate.onNetworkListChanged only occurs on user action (after occurring a few times during startup / resume).

If you can confirm that is not the case, that is definitely a high priority bug that should be addressed independently. Please file a feedback report with attn:stevenjb@ and let me know.

That's largely what the previous bug I filed was about.  I submitted feedback reports and device logs there.  Let me know if you need further data.

The requirement is an API independent of network scanning.  Rather than argue on about the behavior of the existing API, just let me know if you feel this new API is a fit for chrome.networkingPrivate.  If not, we'll take on the work to implement it in a different namespace.

Yes, and as I have explained, all of those, that I am aware of, used:

chrome.networkingPrivate.onNetworksChanged

which is *different* from:

chrome.networkingPrivate.onNetworkListChanged

onNetworksChange is *expected* to occur frequently when a wifi network is connected.

onNetworkListChanged is *not*. And if it does, that is a *bug*.

So, please, if you think that chrome.networkingPrivate.onNetworkListChanged is triggering in the absence of a startup scenario or opening a networking UI element, *please* file a new bug with a repro and file a feedback report.

Closing this again.

I am still unclear what the problem with using chrome.networkingPriave.onNetworkListChanged is.

If there is a confirmed problem, please provide an example JS snippet using *chrome.networkingPriave.onNetworkListChanged* that is triggered during an idle situation (i.e. not login, resume, or after opening the networking UI).