- From: Arvind Jain <arvind@google.com>
- Date: Sat, 24 Aug 2013 18:21:18 -0700
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: Ojan Vafai <ojan@chromium.org>, public-web-perf <public-web-perf@w3.org>
- Message-ID: <CAOYaDdO4=AJBfSWiUJk3Pr+oaxEVVDi3KGo1M138Hmn0UvK=iQ@mail.gmail.com>
Got it. How about visibility of top level browsing context? Would we expose document.parent.visibility across origin? Today we expose it as document.visibility in a cross origin iframe returns that value. On Sat, Aug 24, 2013 at 6:12 PM, Jonas Sicking <jonas@sicking.cc> wrote: > Agreed. It seems quite possible that this won't break any existing content. > > / Jonas > > On Sat, Aug 24, 2013 at 5:55 PM, Ojan Vafai <ojan@chromium.org> wrote: > > Ideally we wouldn't add a new property. So, we should try shipping this > in > > the backwards-incompatible way (i.e. changing the existing property) and > see > > if we can get away with it. > > > > > > On Sat, Aug 24, 2013 at 5:30 PM, Arvind Jain <arvind@google.com> wrote: > >> > >> Is it ok to just update the spec in a non compatible way i.e. in the new > >> version of the spec, we say visibility is at document level (which > would be > >> not backwards compatible). Or do we need to add a new property? > >> > >> Arvind > >> > >> > >> On Sat, Aug 24, 2013 at 5:22 PM, Jonas Sicking <jonas@sicking.cc> > wrote: > >>> > >>> We at mozilla is certainly in support of this. In fact, bz has strongly > >>> argued that this should be the case for a very long time. > >>> > >>> / Jonas > >>> > >>> On Aug 24, 2013 2:11 PM, "Arvind Jain" <arvind@google.com> wrote: > >>>> > >>>> > >>>> Hi, > >>>> I've seen a few requests where developers would like to query for > >>>> visibility of their IFRAME (when the iframe is in third party > context). > >>>> > >>>> Today, in Page Visibility, we set document.visibilityState to "hidden" > >>>> or "visible", but it is really the visibility of the top level > browsing > >>>> context that includes the given document. This information is made > available > >>>> to third party IFRAMEs. > >>>> > >>>> What do folks think of making document.visibilityState the property of > >>>> the document itself instead of the top level browsing context? That > way you > >>>> can detect conditions like when the IFRAME is below the fold and > therefore > >>>> not visible while the top level browsing context itself is visible. > >>>> > >>>> Thanks, > >>>> Arvind > >> > >> > > >
Received on Sunday, 25 August 2013 01:21:46 UTC