[e] (0) Remove now-redundant paragraph.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=20418
Affected topics: CSS, HTML

git-svn-id: http://svn.whatwg.org/webapps@8474 340c8d12-0b0e-0410-8428-c7bf67bfef74

complete.html

@@ -298,7 +298,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 6 February 2014</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 7 February 2014</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -52364,12 +52364,6 @@ <h4 id=the-dialog-element><span class=secno>4.11.7 </span>The <dfn><code>dialog<
   keyword is not a keyword that can be specified in CSS; the 'position' property can only compute to
   this value if the <code><a href=#the-dialog-element>dialog</a></code> element is positioned via the APIs described above.</p>
 
-  <p class=note>Elements positioned in this way are not clipped by the 'overflow' property of
-  ancestors (nor moved by the resulting scrolling mechanisms), since the containing block is the
-  initial containing block. Anchoring to an element that <em>is</em> so clipped (and shifted) can
-  therefore result in unexpected effects (where the anchored element moves along with the clipped
-  element, but isn't itself clipped).</p>
-
   <p>User agents in visual interactive media should allow the user to pan the viewport to access all
   parts of a <code><a href=#the-dialog-element>dialog</a></code> element's border box, even if the element is larger than the
   viewport and the viewport would otherwise not have a scroll mechanism (e.g. because the viewport's

index

@@ -298,7 +298,7 @@
 
   <header class=head id=head><p><a href=http://www.whatwg.org/ class=logo><img width=101 src=/images/logo alt=WHATWG height=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 6 February 2014</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 7 February 2014</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -52364,12 +52364,6 @@ dictionary <dfn id=relatedeventinit>RelatedEventInit</dfn> : <a href=#eventinit>
   keyword is not a keyword that can be specified in CSS; the 'position' property can only compute to
   this value if the <code><a href=#the-dialog-element>dialog</a></code> element is positioned via the APIs described above.</p>
 
-  <p class=note>Elements positioned in this way are not clipped by the 'overflow' property of
-  ancestors (nor moved by the resulting scrolling mechanisms), since the containing block is the
-  initial containing block. Anchoring to an element that <em>is</em> so clipped (and shifted) can
-  therefore result in unexpected effects (where the anchored element moves along with the clipped
-  element, but isn't itself clipped).</p>
-
   <p>User agents in visual interactive media should allow the user to pan the viewport to access all
   parts of a <code><a href=#the-dialog-element>dialog</a></code> element's border box, even if the element is larger than the
   viewport and the viewport would otherwise not have a scroll mechanism (e.g. because the viewport's

source

@@ -57892,12 +57892,6 @@ dictionary <dfn>RelatedEventInit</dfn> : <span>EventInit</span> {
   keyword is not a keyword that can be specified in CSS; the 'position' property can only compute to
   this value if the <code>dialog</code> element is positioned via the APIs described above.</p>
 
-  <p class="note">Elements positioned in this way are not clipped by the 'overflow' property of
-  ancestors (nor moved by the resulting scrolling mechanisms), since the containing block is the
-  initial containing block. Anchoring to an element that <em>is</em> so clipped (and shifted) can
-  therefore result in unexpected effects (where the anchored element moves along with the clipped
-  element, but isn't itself clipped).</p>
-
   <p>User agents in visual interactive media should allow the user to pan the viewport to access all
   parts of a <code>dialog</code> element's border box, even if the element is larger than the
   viewport and the viewport would otherwise not have a scroll mechanism (e.g. because the viewport's