- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 6 Oct 2011 17:23:41 -0700
- To: Jatinder Mann <jmann@microsoft.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-web-perf@w3.org" <public-web-perf@w3.org>
But if a document is hidden, due to it's iframe being display:none, wouldn't we want the code in that document to go into resource-saving mode? Say that a page updates itself every minute any time it's displayed. But only while the page is displayed. When hidden it only updates itself every 30 minutes in order to save CPU and bandwidth. If someone puts such a page in an iframe that is display:none, wouldn't you want the page to only update itself every 30 minutes? / Jonas On Thu, Oct 6, 2011 at 4:24 PM, Jatinder Mann <jmann@microsoft.com> wrote: > I think so. This behavior makes it clear that the iframe's visibility is tied with the top level document. This is the current behavior in both IE10 and Chrome. > > Jatinder > > -----Original Message----- > From: Boris Zbarsky [mailto:bzbarsky@MIT.EDU] > Sent: Wednesday, October 05, 2011 8:28 PM > To: Jatinder Mann > Cc: public-web-perf@w3.org > Subject: Re: [PageVisibility] What should the visibility api return in display:none iframes? > > On 10/5/11 7:01 PM, Jatinder Mann wrote: >> We define the visibility as that of the top level browsing context; all connected documents, like iframes, must return the same value. > > Yes, I'm aware this is what the spec says right now. What I'm asking is > whether this is _desirable_. > > -Boris > > >
Received on Friday, 7 October 2011 00:24:46 UTC