[html5] r5226 - [e] (0) Various minor fixes and an elaboration of an example.
whatwg at whatwg.org
whatwg at whatwg.org
Thu Jul 29 18:37:41 PDT 2010
Author: ianh
Date: 2010-07-29 18:37:40 -0700 (Thu, 29 Jul 2010)
New Revision: 5226
Modified:
complete.html
index
source
Log:
[e] (0) Various minor fixes and an elaboration of an example.
Modified: complete.html
===================================================================
--- complete.html 2010-07-30 00:09:20 UTC (rev 5225)
+++ complete.html 2010-07-30 01:37:40 UTC (rev 5226)
@@ -16041,6 +16041,27 @@
<p>Both of the documents above are semantically identical and would
produce the same outline in compliant user agents.</p>
+ <p>This third example is also semantically identical, and might be
+ easier to maintain (e.g. if sections are often moved around in
+ editing):</p>
+
+ <pre><body>
+ <h1>Apples</h1>
+ <p>Apples are fruit.</p>
+ <section>
+ <h1>Taste</h1>
+ <p>They taste lovely.</p>
+ <section>
+ <h1>Sweet</h1>
+ <p>Red apples are sweeter than green ones.</p>
+ </section>
+ </section>
+ <section>
+ <h1>Color</h1>
+ <p>Apples come in various colors.</p>
+ </section>
+</body></pre>
+
</div>
@@ -21522,19 +21543,18 @@
original parent <code><a href=#document>Document</a></code> if its <code><a href=#the-iframe-element>iframe</a></code> is
moved to another <code><a href=#document>Document</a></code>.</p>
- <p>On the other hand, if an <code><a href=#the-iframe-element>iframe</a></code> is <span class=note><a href=#remove-an-element-from-a-document title="remove an element from a
- document">removed</a> from a <code><a href=#document>Document</a></code> and is then
- subsequently garbage collected, this will likely mean (in the
- absence of other references) that the <a href=#child-browsing-context>child browsing
- context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object will become
- eligble for garbage collection, which will then lead to that
- <a href=#browsing-context>browsing context</a> being <a href=#a-browsing-context-is-discarded title="a browsing context
- is discarded">discarded</a>, which will then lead to its
- <code><a href=#document>Document</a></code> being <a href=#discard-a-document title="discard a
+ <p>On the other hand, if an <code><a href=#the-iframe-element>iframe</a></code> is <a href=#remove-an-element-from-a-document title="remove an element from a document">removed</a> from a
+ <code><a href=#document>Document</a></code> and is then subsequently garbage collected,
+ this will likely mean (in the absence of other references) that the
+ <a href=#child-browsing-context>child browsing context</a>'s <code><a href=#windowproxy>WindowProxy</a></code>
+ object will become eligble for garbage collection, which will then
+ lead to that <a href=#browsing-context>browsing context</a> being <a href=#a-browsing-context-is-discarded title="a
+ browsing context is discarded">discarded</a>, which will then
+ lead to its <code><a href=#document>Document</a></code> being <a href=#discard-a-document title="discard a
document">discarded</a> also. This happens without notice to any
scripts running in that <code><a href=#document>Document</a></code>; for example, no
<code title=event-unload>unload</code> events are fired (the
- "<a href=#unload-a-document>unload a document</a>" steps are not run).</span></p>
+ "<a href=#unload-a-document>unload a document</a>" steps are not run).</p>
</div>
@@ -30512,8 +30532,8 @@
unrecognized value is given, then the user agent must raise a
<code><a href=#syntax_err>SYNTAX_ERR</a></code> exception. User agents must recognize the
four values described above exactly (e.g. they must not do case
- folding). The method must return a <code><a href=#canvaspattern>CanvasPattern</a></code> object
- suitably initialized.</p>
+ folding). Except as specified below, the method must return a
+ <code><a href=#canvaspattern>CanvasPattern</a></code> object suitably initialized.</p>
<p>The <var title="">image</var> argument is an instance of either
<code><a href=#htmlimageelement>HTMLImageElement</a></code>, <code><a href=#htmlcanvaselement>HTMLCanvasElement</a></code>, or
Modified: index
===================================================================
--- index 2010-07-30 00:09:20 UTC (rev 5225)
+++ index 2010-07-30 01:37:40 UTC (rev 5226)
@@ -15965,6 +15965,27 @@
<p>Both of the documents above are semantically identical and would
produce the same outline in compliant user agents.</p>
+ <p>This third example is also semantically identical, and might be
+ easier to maintain (e.g. if sections are often moved around in
+ editing):</p>
+
+ <pre><body>
+ <h1>Apples</h1>
+ <p>Apples are fruit.</p>
+ <section>
+ <h1>Taste</h1>
+ <p>They taste lovely.</p>
+ <section>
+ <h1>Sweet</h1>
+ <p>Red apples are sweeter than green ones.</p>
+ </section>
+ </section>
+ <section>
+ <h1>Color</h1>
+ <p>Apples come in various colors.</p>
+ </section>
+</body></pre>
+
</div>
@@ -21446,19 +21467,18 @@
original parent <code><a href=#document>Document</a></code> if its <code><a href=#the-iframe-element>iframe</a></code> is
moved to another <code><a href=#document>Document</a></code>.</p>
- <p>On the other hand, if an <code><a href=#the-iframe-element>iframe</a></code> is <span class=note><a href=#remove-an-element-from-a-document title="remove an element from a
- document">removed</a> from a <code><a href=#document>Document</a></code> and is then
- subsequently garbage collected, this will likely mean (in the
- absence of other references) that the <a href=#child-browsing-context>child browsing
- context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object will become
- eligble for garbage collection, which will then lead to that
- <a href=#browsing-context>browsing context</a> being <a href=#a-browsing-context-is-discarded title="a browsing context
- is discarded">discarded</a>, which will then lead to its
- <code><a href=#document>Document</a></code> being <a href=#discard-a-document title="discard a
+ <p>On the other hand, if an <code><a href=#the-iframe-element>iframe</a></code> is <a href=#remove-an-element-from-a-document title="remove an element from a document">removed</a> from a
+ <code><a href=#document>Document</a></code> and is then subsequently garbage collected,
+ this will likely mean (in the absence of other references) that the
+ <a href=#child-browsing-context>child browsing context</a>'s <code><a href=#windowproxy>WindowProxy</a></code>
+ object will become eligble for garbage collection, which will then
+ lead to that <a href=#browsing-context>browsing context</a> being <a href=#a-browsing-context-is-discarded title="a
+ browsing context is discarded">discarded</a>, which will then
+ lead to its <code><a href=#document>Document</a></code> being <a href=#discard-a-document title="discard a
document">discarded</a> also. This happens without notice to any
scripts running in that <code><a href=#document>Document</a></code>; for example, no
<code title=event-unload>unload</code> events are fired (the
- "<a href=#unload-a-document>unload a document</a>" steps are not run).</span></p>
+ "<a href=#unload-a-document>unload a document</a>" steps are not run).</p>
</div>
@@ -30439,8 +30459,8 @@
unrecognized value is given, then the user agent must raise a
<code><a href=#syntax_err>SYNTAX_ERR</a></code> exception. User agents must recognize the
four values described above exactly (e.g. they must not do case
- folding). The method must return a <code><a href=#canvaspattern>CanvasPattern</a></code> object
- suitably initialized.</p>
+ folding). Except as specified below, the method must return a
+ <code><a href=#canvaspattern>CanvasPattern</a></code> object suitably initialized.</p>
<p>The <var title="">image</var> argument is an instance of either
<code><a href=#htmlimageelement>HTMLImageElement</a></code>, <code><a href=#htmlcanvaselement>HTMLCanvasElement</a></code>, or
Modified: source
===================================================================
--- source 2010-07-30 00:09:20 UTC (rev 5225)
+++ source 2010-07-30 01:37:40 UTC (rev 5226)
@@ -16941,6 +16941,27 @@
<p>Both of the documents above are semantically identical and would
produce the same outline in compliant user agents.</p>
+ <p>This third example is also semantically identical, and might be
+ easier to maintain (e.g. if sections are often moved around in
+ editing):</p>
+
+ <pre><body>
+ <h1>Apples</h1>
+ <p>Apples are fruit.</p>
+ <section>
+ <h1>Taste</h1>
+ <p>They taste lovely.</p>
+ <section>
+ <h1>Sweet</h1>
+ <p>Red apples are sweeter than green ones.</p>
+ </section>
+ </section>
+ <section>
+ <h1>Color</h1>
+ <p>Apples come in various colors.</p>
+ </section>
+</body></pre>
+
</div>
@@ -22912,16 +22933,15 @@
original parent <code>Document</code> if its <code>iframe</code> is
moved to another <code>Document</code>.</p>
- <p>On the other hand, if an <code>iframe</code> is <span <p
- class="note"><span title="remove an element from a
- document">removed</span> from a <code>Document</code> and is then
- subsequently garbage collected, this will likely mean (in the
- absence of other references) that the <span>child browsing
- context</span>'s <code>WindowProxy</code> object will become
- eligble for garbage collection, which will then lead to that
- <span>browsing context</span> being <span title="a browsing context
- is discarded">discarded</span>, which will then lead to its
- <code>Document</code> being <span title="discard a
+ <p>On the other hand, if an <code>iframe</code> is <span
+ title="remove an element from a document">removed</span> from a
+ <code>Document</code> and is then subsequently garbage collected,
+ this will likely mean (in the absence of other references) that the
+ <span>child browsing context</span>'s <code>WindowProxy</code>
+ object will become eligble for garbage collection, which will then
+ lead to that <span>browsing context</span> being <span title="a
+ browsing context is discarded">discarded</span>, which will then
+ lead to its <code>Document</code> being <span title="discard a
document">discarded</span> also. This happens without notice to any
scripts running in that <code>Document</code>; for example, no
<code title="event-unload">unload</code> events are fired (the
@@ -33468,8 +33488,8 @@
unrecognized value is given, then the user agent must raise a
<code>SYNTAX_ERR</code> exception. User agents must recognize the
four values described above exactly (e.g. they must not do case
- folding). The method must return a <code>CanvasPattern</code> object
- suitably initialized.</p>
+ folding). Except as specified below, the method must return a
+ <code>CanvasPattern</code> object suitably initialized.</p>
<p>The <var title="">image</var> argument is an instance of either
<code>HTMLImageElement</code>, <code>HTMLCanvasElement</code>, or
More information about the Commit-Watchers
mailing list