Re: making page visibility a property of document instead of top level browsing context

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
>>>
>>
>