W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2015

[powerful-features] Talking about the "incumbent settings object" of a document makes no sense

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Wed, 01 Jul 2015 10:52:38 -0400
Message-ID: <5593FEB6.3000603@mit.edu>
To: public-webappsec@w3.org
https://w3c.github.io/webappsec/specs/powerfulfeatures/#settings-secure 
step 2.2.2 talks about "ancestor’s incumbent settings object" where 
"ancestor" is a document.  But "incumbent settings object" is a property 
of the JS callstack, not of a document.

I assume that what you mean here is the "relevant settings object" of 
the document's global or something along those lines?  But mail coming 
up about how this whole part of the algorithm is not necessarily sensical...

-Boris
Received on Wednesday, 1 July 2015 14:53:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:13 UTC