hixie: showModalDialog() inside a sandboxed iframe should be blocked _before_ the window pops up... Also, some minor editorial cleanup in this area. (whatwg r6233)

hixie: showModalDialog() inside a sandboxed iframe should be blocked
_before_ the window pops up... Also, some minor editorial cleanup in
this area. (whatwg r6233)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4996&r2=1.4997&f=h
http://html5.org/tools/web-apps-tracker?from=6232&to=6233

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4996
retrieving revision 1.4997
diff -u -d -r1.4996 -r1.4997
--- Overview.html 15 Jun 2011 05:55:13 -0000 1.4996
+++ Overview.html 15 Jun 2011 06:28:19 -0000 1.4997
@@ -20175,8 +20175,8 @@
 
     <p>This flag also <a href="#sandboxWindowOpen">prevents content
     from creating new auxiliary browsing contexts</a>, e.g. using the
-    <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code> attribute or the
-    <code title="dom-open"><a href="#dom-open">window.open()</a></code> method.</p>
+    <code title="attr-hyperlink-target"><a href="#attr-hyperlink-target">target</a></code> attribute, the
+    <code title="dom-open"><a href="#dom-open">window.open()</a></code> method, or the <code title="dom-showModalDialog"><a href="#dom-showmodaldialog">showModalDialog()</a></code> method.</p>
 
    </dd>
 
@@ -43475,10 +43475,11 @@
    <li>
 
     <p>Otherwise, a new browsing context is being requested, and what
-    happens depends on the user agent's configuration and/or
-    abilities:</p>
+    happens depends on the user agent's configuration and/or abilities
+    &mdash; it is determined by the rules given for the first
+    applicable option from the following list:</p>
 
-    <dl><dt id="sandboxWindowOpen">If the current browsing context had
+    <dl class="switch"><dt id="sandboxWindowOpen">If the current browsing context had
      the <a href="#sandboxed-navigation-browsing-context-flag">sandboxed navigation browsing context flag</a> set
      when its <a href="#active-document">active document</a> was created.</dt>
 
@@ -43487,9 +43488,10 @@
      browsing context</a>. If the user picks one of those options,
      then the designated browsing context must be the chosen one (the
      browsing context's name isn't set to the given browsing context
-     name). Otherwise (if the user agent doesn't offer the option to
-     the user, or if the user declines to allow a browsing context to
-     be used) there must not be a chosen browsing context.</dd>
+     name). The default behaviour (if the user agent doesn't offer the
+     option to the user, or if the user declines to allow a browsing
+     context to be used) there must not be a chosen browsing
+     context.</dd>
 
 
      <dt id="noopener">If the user agent has been configured such that
@@ -50649,6 +50651,15 @@
 
    <li>
 
+    <p>If the current browsing context had the <a href="#sandboxed-navigation-browsing-context-flag">sandboxed
+    navigation browsing context flag</a> set when its <a href="#active-document">active
+    document</a> was created, then return the empty string and
+    abort these steps.</p>
+
+   </li>
+
+   <li>
+
     <p>Let <var title="">the list of background browsing
     contexts</var> be a list of all the browsing contexts that:</p>

Received on Friday, 17 June 2011 09:52:20 UTC