- From: James Simonsen <simonjam@chromium.org>
- Date: Wed, 11 Jul 2012 17:21:30 -0700
- To: Andy Davies <dajdavies@gmail.com>
- Cc: public-web-perf@w3.org
Received on Thursday, 12 July 2012 00:21:58 UTC
On Fri, Jun 29, 2012 at 11:41 AM, Andy Davies <dajdavies@gmail.com> wrote: > One of the current challenges is understanding how much latency is > introduced by the delay involved in waking the radio in wireless devices > from power saving modes. > > My guess is that the information required to create a radioAwake attribute > as part of Navigation (and Resource Timing) isn't exposed to the browser > but would be interested in other thoughts and comments. It definitely sounds useful and the sort of thing that'd be exposed in these specs. It's a little unique in that it requires the OS to comply. It may be tricky to implement for that reason. You could imagine the same thing being useful on a laptop too if the wifi was still waking up from sleep. Maybe it should just be a general networkAvailable? James
Received on Thursday, 12 July 2012 00:21:58 UTC