W3C home > Mailing lists > Public > public-webappsec@w3.org > October 2014

Re: Frame Ancestors and Referrer (Re: [webappsec] Call for Consensus: Stop work on Content Security Policy 1.0, transition to WG Note)

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Fri, 24 Oct 2014 14:48:12 -0400
Message-ID: <544A9EEC.8060706@mit.edu>
To: public-webappsec@w3.org
On 10/24/14, 7:13 AM, Anne van Kesteren wrote:
> We might be ready to reconsider this.

For some values of "we"... ;)

> I was wondering though whether
> the API can still be made asynchronous given everyone's out-of-process
> <iframe> aspirations.

Why bother?

The returned thing is an invariant of the browsing context (and hence of 
any Window in that browsing context, etc).  So you can just save it when 
initially creating the browsing context and then you always have it 
in-process when you need it, I think.

Received on Friday, 24 October 2014 18:48:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:41 UTC