W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2011

Re: Visibility API

From: Christian Biesinger <cbiesinger@gmail.com>
Date: Wed, 16 Feb 2011 10:57:05 -0800
Message-ID: <AANLkTinb61wwT5yERHR59eWycPvDyPA2ZJVudJMUKSU1@mail.gmail.com>
To: Arvind Jain <arvind@google.com>
Cc: public-web-perf <public-web-perf@w3.org>
link rel=prefetch doesn't execute any scripts on the prefetched page,
at least not in Firefox. Is this different in chrome?

This does seem like a useful API for web pages though.

-christian

On Wed, Feb 16, 2011 at 6:30 AM, Arvind Jain <arvind@google.com> wrote:
> Hi webperf folks,
> I'd like to check with you if it would make sense to add one more
> deliverable to the web performance working group.
> There's been a proposal for a Tab Visibility API, which provides a web
> developer an API (in Javascript) to find out whether the page is currently
> hidden (e.g. not in the foreground tab) vs. visible to the user.
> I'm aware of two performance use cases for it:
> 1) pages that consume a lot of CPU can avoid doing so when the page is not
> visible to the user.
> 2) support html5 <link rel=prefetch> standard (when the browser prefetches a
> page, it should let the page know it's not visible).
> Below is the discussion on it on whatwg:
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-December/029382.html
> I think it makes sense for web performance working group to standardize this
> API. Please let me know your thoughts.
> Thanks,
> Arvind
Received on Wednesday, 16 February 2011 18:57:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:29 UTC