hixie: update for pub issues

hixie: update for pub issues

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4566&r2=1.4567&f=h

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4566
retrieving revision 1.4567
diff -u -d -r1.4566 -r1.4567
--- Overview.html 2 Dec 2010 07:15:40 -0000 1.4566
+++ Overview.html 6 Dec 2010 22:18:24 -0000 1.4567
@@ -41415,8 +41415,10 @@
   <a href="#browsing-context">browsing context</a> <var title="">b</var> must return the
   <code><a href="#windowproxy">WindowProxy</a></code> object of its <a href="#top-level-browsing-context">top-level browsing
   context</a> (which would be its own <code><a href="#windowproxy">WindowProxy</a></code>
-  object if it was a <a href="#top-level-browsing-context">top-level browsing context</a>
-  itself).</p>
+  object if it was a <a href="#top-level-browsing-context">top-level browsing context</a> itself),
+  if it has one, or its own <code><a href="#windowproxy">WindowProxy</a></code> object otherwise
+  (e.g. if it was a detached <a href="#nested-browsing-context">nested browsing
+  context</a>).</p>
 
   <p>The <dfn id="dom-parent" title="dom-parent"><code>parent</code></dfn> IDL
   attribute on the <code><a href="#window">Window</a></code> object of a
@@ -41425,7 +41427,8 @@
   <var title="">b</var> is a <a href="#child-browsing-context">child browsing context</a>), or
   the <code><a href="#windowproxy">WindowProxy</a></code> object of the <a href="#browsing-context">browsing
   context</a> <var title="">b</var> itself, otherwise (i.e. if it
-  is a <a href="#top-level-browsing-context">top-level browsing context</a>).</p>
+  is a <a href="#top-level-browsing-context">top-level browsing context</a> or a detached
+  <a href="#nested-browsing-context">nested browsing context</a>).</p>
 
   <p>The <dfn id="dom-frameelement" title="dom-frameElement"><code>frameElement</code></dfn>
   IDL attribute on the <code><a href="#window">Window</a></code> object of a
@@ -41433,11 +41436,11 @@
   the following algorithm:</p>
 
   <ol><li><p>If <var title="">d</var> is not a <code><a href="#document">Document</a></code> in a
-   <a href="#child-browsing-context">child browsing context</a>, return null and abort these
+   <a href="#nested-browsing-context">nested browsing context</a>, return null and abort these
    steps.</li>
 
-   <li><p>If the <a href="#parent-browsing-context">parent browsing context</a>'s <a href="#active-document">active
-   document</a> does not have the <a href="#same-origin" title="same
+   <li><p>If the <a href="#browsing-context-container">browsing context container</a>'s
+   <code><a href="#document">Document</a></code> does not have the <a href="#same-origin" title="same
    origin">same</a> <a href="#effective-script-origin">effective script origin</a> as the
    <a href="#entry-script">entry script</a>, then throw a <code><a href="#security_err">SECURITY_ERR</a></code>
    exception.</li>
@@ -65451,7 +65454,14 @@
   as an independent set of one or more bidirectional algorithm
   paragraphs when displayed, as defined by the bidirectional
   algorithm, including, for instance, supporting the
-  paragraph-breaking behaviour of U+000A LINE FEED (LF) characters. <a href="#refsBIDI">[BIDI]</a></p>
+  paragraph-breaking behaviour of U+000A LINE FEED (LF) characters.
+  For the purposes of determining the paragraph level of such text in
+  the bidirectional algorithm, this specification does <em>not</em>
+  provide a higher-level override of rules P2 and P3. <a href="#refsBIDI">[BIDI]</a></p>
+
+  <p>When necessary, authors can enforce a particular direction for a
+  given paragraph by starting it with the Unicode U+200E LEFT-TO-RIGHT
+  MARK or U+200F RIGHT-TO-LEFT MARK characters.</p>
 
   <div class="example">
 
@@ -65471,7 +65481,8 @@
 
    <p>For a more complex example, consider the following script:</p>
 
-   <pre>var s;
+   <pre class="bad">/* Warning: this script does not handle right-to-left scripts correctly */
+var s;
 if (s = prompt('What is your name?')) {
   alert(s + '! Ok, Fred, ' + s + ', and Wilma will get the car.');
 }</pre>
@@ -65480,13 +65491,19 @@
    alert "<samp>Kitty! Ok, Fred, Kitty, and Wilma will get the
    car.</samp>". However, if the user enters "<kbd dir="rtl" lang="ar">&#1604;&#1575;&nbsp;&#1571;&#1601;&#1607;&#1605;</kbd>",
    then the bidirectional algorithm will determine that the direction
-   of the paragraph is right-to-left, and so the output will be "<samp lang=""><bdo dir="rtl">&#1604;&#1575;&nbsp;&#1571;&#1601;&#1607;&#1605;!&nbsp;derF&nbsp;,kO,&nbsp;&#1604;&#1575;&nbsp;&#1571;&#1601;&#1607;&#1605;,&nbsp;rac&nbsp;eht&nbsp;teg&nbsp;lliw&nbsp;amliW&nbsp;dna.</bdo></samp>"!</p>
+   of the paragraph is right-to-left, and so the output will be the
+   following unintended mess: "<samp lang=""><bdo dir="rtl">&#1604;&#1575;&nbsp;&#1571;&#1601;&#1607;&#1605;!&nbsp;derF&nbsp;,kO,&nbsp;&#1604;&#1575;&nbsp;&#1571;&#1601;&#1607;&#1605;,&nbsp;rac&nbsp;eht&nbsp;teg&nbsp;lliw&nbsp;amliW&nbsp;dna.</bdo></samp>"</p>
 
-  </div>
+   <p>To force an alert that starts with user-provided text (or other
+   text of unknown directionality) to render left-to-right, the string
+   can be prefixed with a U+200E LEFT-TO-RIGHT MARK character:</p>
 
-  <p>When necessary, authors can enforce a particular direction for a
-  given paragraph by starting it with the Unicode U+200E LEFT-TO-RIGHT
-  MARK or U+200F RIGHT-TO-LEFT MARK characters.</p>
+   <pre>var s;
+if (s = prompt('What is your name?')) {
+  alert('<strong>\u200E</strong>' + s + '! Ok, Fred, ' + s + ', and Wilma will get the car.');
+}</pre>
+
+  </div>

Received on Monday, 6 December 2010 22:21:00 UTC