You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copying related questions from blink-dev thread...
In the code it looks like downlink, rtt and effectiveType all fall back to other values when "not observing," e.g. rtt will be 0. In practice, would this happen every time the phone has been turned off for 5 minutes, or in some much rarer circumstance?
It seems reasonable to have this fallback, so that users of the API can just use the values and have things work well enough. Absent any randomization, it will mean that it's possible to tell when the device hasn't been recently active at all, is that worth spelling out in https://wicg.github.io/netinfo/#privacy-considerations?
Yes, the renderer returns 0 as the RTT estimate when a value is not available from the network state notifier in Blink. However, this is an artifact of implementation, and in practice, by the time the JS API is called, a non-zero estimate would be available. https://bugs.chromium.org/p/chromium/issues/detail?id=728771 has more details.
https://wicg.github.io/netinfo/#dom-networkinformation-rtt
This is what the implementation in Chromium does, but starting from the spec I can't find that this should be the case.
Should it be the case? Maybe the value matching the
effectiveType
should be used? https://wicg.github.io/netinfo/#effective-connection-typesThe text was updated successfully, but these errors were encountered: