Re: [PageVisibility] What should the visibility api return in display:none iframes?

If we want to include display none, why not consider other visibility cases
- All of which would probably benefit web developers. I think the idea was
to keep the page visibility consistent and simple.


On Fri, Oct 7, 2011 at 10:23 AM, Jonas Sicking <> wrote:

> On Fri, Oct 7, 2011 at 10:21 AM, Jatinder Mann <>
> 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 20:37:19 UTC