Skip to content

Commit

Permalink
POWER: Clarify ancestor settings objects.
Browse files Browse the repository at this point in the history
In https://lists.w3.org/Archives/Public/public-webappsec/2015Jul/0011.html,
Boris Zbarsky noted that talking about the incumbent settings object of
an ancestor Document makes no sense. Switching the language to point at
the relevant settings object of each ancestor document's global object.
  • Loading branch information
mikewest committed Jul 2, 2015
1 parent 1a8c1cc commit a9c195b
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions specs/powerfulfeatures/index.src.html
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,7 @@ <h1>Secure Contexts</h1>
text: incumbent settings object
text: responsible document
text: settings object
text: relevant settings object; url: relevant-settings-object-for-a-global-object
type: attribute
urlPrefix: webstorage.html
text: sessionStorage; for: WindowSessionStorage; url: the-sessionstorage-attribute
Expand Down Expand Up @@ -421,8 +422,9 @@ <h3 id="settings-secure">
<var>ancestor</var>.
</li>
<li>
If <var>ancestor</var>'s <a>incumbent settings object</a>'s
<a>TLS State</a> is <code>Authenticated</code>, skip to the next
If the <a>relevant settings object</a> for <var>ancestor</var>'s
<a>global object</a> has a <a>TLS State</a> of
<code>Authenticated</code>, skip to the next
<var>ancestor</var>.
</li>
<li>
Expand Down

0 comments on commit a9c195b

Please sign in to comment.