From 4c64a55ba9046b64568a39b3986517b59d3101fc Mon Sep 17 00:00:00 2001
From: Mike West <mkwst@google.com>
Date: Sat, 16 Jul 2016 07:59:14 +0200
Subject: [PATCH] Creator context security landed.

Closes w3c/webappsec-secure-contexts#37.
---
 index.src.html | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

diff --git a/index.src.html b/index.src.html
index e5ee580..843ca1d 100644
--- a/index.src.html
+++ b/index.src.html
@@ -109,8 +109,13 @@ <h1>Secure Contexts</h1>
     text: exposed; url: dfn-exposed
     text: [SecureContext]; url: SecureContext
 
-spec: HTML; urlPrefix: https://html.spec.whatwg.org/multipage/semantics.html
-  type: dfn; text: noopener; url: link-type-noopener
+spec: HTML; urlPrefix: https://html.spec.whatwg.org/multipage/
+  urlPrefix: browsers.html
+    type: dfn;
+      text: creator context security
+  urlPrefix: semantics.html
+    type: dfn;
+      text: noopener; url: link-type-noopener
 </pre>
 <pre class="biblio">
 {
@@ -716,11 +721,9 @@ <h3 id="settings-object">
       status, a popups' status depends on how it is opened, as discussed
       in [[#examples-top-level]].
 
-      ISSUE(whatwg/html#1561): The 'creator context security' concept doesn't
-      yet exist, other than in an open PR against WHATWG's HTML.
-
-      ISSUE(w3c/html#524): The 'creator context security' concept doesn't yet
-      exist in W3C's HTML.
+      ISSUE(w3c/html#524): The 'creator context security' concept landed in
+      WHATWG's HTML in <a href="https://github.com/whatwg/html/pull/1561">whatwg/html#1561</a>,
+      but doesn't yet exist in W3C's HTML.
 
   5.  If |settings object|'s <a>HTTPS state</a> is "`modern`", return
       "`Secure`".