Re: [Navigation Timing] Adding radioAwake attribute

On 29 June 2012 21:20, Ilya Grigorik <> wrote:
> +1. It's always a gamble on mobile today to figure out if you're going to
> incur the extra cost of waiting for radio, or not.. which adds a significant
> amount of latency to the connection. Not sure if it's also useful to
> explicitly distinguish "low power" vs "sleep" modes, but at the very least,
> "radioAcquire{start, end}" events are much needed additions to both specs.
> ig
> P.S. radioAcquire* is likely not the right name.

Does it need a new start attribute - won't it be the same as
fetchStart in navigation timing?


Received on Wednesday, 4 July 2012 18:00:22 UTC