Re: [PageVisibility] What should the visibility api return in display:none iframes? from Jonas Sicking on 2011-10-07 (public-web-perf@w3.org from October 2011)

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 7 Oct 2011 10:23:59 -0700
To: Jatinder Mann <jmann@microsoft.com>
Cc: Anne van Kesteren <annevk@opera.com>, Arvind Jain <arvind@google.com>, Boris Zbarsky <bzbarsky@mit.edu>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <CA+c2ei9sJ=Faz_ZVU6+f+-8ejWmrKYgcUntqOX5-DZYwFp4JpQ@mail.gmail.com>

On Fri, Oct 7, 2011 at 10:21 AM, Jatinder Mann <jmann@microsoft.com> wrote:
> That was my initial impression also. Further, if we begin including formatting information for sub-documents, why not include element visibility? E.g, my canvas element has been scrolled off page, so I should stop my animation.

We're doing that in the .requestAnimationFrame API, no?

> Scoping this API to the visibility of the top level document, as it is now, keeps it simple and still very useful in creating power- and CPU- efficient applications, particularly in the cases where the user choses to hide the page from view by interacting with the browser.

Again, what's the benefit to web developers compared to taking
display:none into account?

/ Jonas

Received on Friday, 7 October 2011 17:24:57 UTC