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

RE: Page Visibility Simplifications

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 22 Jun 2011 22:15:40 +0000
To: Bret Gorsline <bret.gorsline@cbsinteractive.com>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <EE4C13A1D11CFA49A58343DE361B0B040687AB89@TK5EX14MBXC252.redmond.corp.microsoft.com>
Bret,

In the scenario that you have described below, you would probably want to rely solely on the boolean attribute document.hidden - it is false when the page is visible (e.g., browser is not minimized) and true in all other cases, including if the page is hidden but a preview is shown or a prerendered page is created. I think we are leaning towards keeping both states available in the document.visibilityState attribute, but will be evangelizing document.hidden as the common use case of Page Visibility.

It's great to have someone with an ad background give feedback on this API. Thanks!

Jatinder Mann

-----Original Message-----
From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Bret Gorsline
Sent: Tuesday, June 21, 2011 3:07 PM
To: public-web-perf@w3.org
Subject: Re: Page Visibility Simplifications

An ad perspective: we'd like to be able to avoid tracking until the user sees an ad in full size. Ad systems should be able to avoid tracking when the page is hidden or much smaller than full size. If this is what the 'preview' status is for, then I'd like to see it kept.

The 'pre-render' status seems less clearly useful. Maybe some application in analyzing (and controlling) CDN cost against revenue, but it does seem counter to why a browser might want to pre-render in the first place. From a tracking perspective, I think 'hidden' covers this case well enough.

Bret
Received on Wednesday, 22 June 2011 22:16:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 22 June 2011 22:16:20 GMT