Currently, when a render is created, BrowserOnlineStateObserver listens to that event, and notifies the render of the current network state (type, downlinkMax, rtt, downlink, effectiveType).
Also, when a renderer is created, NetworkInformation class queries the
NetworkStateNotifier for the current network state in its ctor.

However, when the *first* renderer is created, there is a race between: (i) The render getting created; and, (ii) IPC from BrowserOnlineStateObserver to renderer on the current network state. This race may sometimes cause the renderer to have no valid network state.

I suspect this affects only the first renderer. So, marking this as P3.
 

Currently, when a renderer is created, BrowserOnlineStateObserver listens to that event, and notifies the renderer of the current network state (type, downlinkMax, rtt, downlink, effectiveType).
Also, recall that when a renderer is created, NetworkInformation class queries the NetworkStateNotifier for the current network state in its ctor.

However, when the *first* renderer is created, there is a race between: (i) The renderer getting created; and, (ii) IPC from BrowserOnlineStateObserver to renderer about the current network state. This race may sometimes cause the renderer to have no valid network state.

One way to fix this race is to pass the network state in the renderer creation IPC.

I suspect this affects only the first renderer. So, marking this as P3.