- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 14 Feb 2010 09:47:06 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv24263
Modified Files:
Overview.html infrastructure.html spec.html tabular-data.html
Log Message:
Clarify the <colgroup> content model's interaction with span=''. (whatwg r4726)
[updated by splitter]
Index: infrastructure.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/infrastructure.html,v
retrieving revision 1.565
retrieving revision 1.566
diff -u -d -r1.565 -r1.566
--- infrastructure.html 1 Feb 2010 23:27:19 -0000 1.565
+++ infrastructure.html 14 Feb 2010 09:47:03 -0000 1.566
@@ -396,10 +396,13 @@
events, as in the DOM Events specifications. The term <dfn id="concept-events-trusted" title="concept-events-trusted">trusted event</dfn> is used as
defined by the DOM Events specification. <!--
http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href="references.html#refsDOMEVENTS">[DOMEVENTS]</a></p><h4 id="plugins"><span class="secno">2.1.5 </span>Plugins</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>The term <dfn id="plugin">plugin</dfn> is used to mean any content handler
- for Web content types that are either not supported by the user
- agent natively or that do not expose a DOM, which supports rendering
- the content as part of the user agent's interface.</p><p>Typically such content handlers are provided by third
- parties.</p><p class="example">One example of a plugin would be a PDF viewer
+ that supports displaying content as part of the user agent's
+ rendering of a <code>Document</code> object, but that neither acts
+ as a <a href="browsers.html#child-browsing-context">child browsing context</a> of the
+ <code>Document</code> nor introduces any <code>Node</code> objects
+ to the <code>Document</code>'s DOM.</p><p>Typically such content handlers are provided by third parties,
+ though a user agent can designate content handlers to be
+ plugins.</p><p class="example">One example of a plugin would be a PDF viewer
that is instantiated in a <a href="browsers.html#browsing-context">browsing context</a> when the
user navigates to a PDF file. This would count as a plugin
regardless of whether the party that implemented the PDF viewer
Index: tabular-data.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/tabular-data.html,v
retrieving revision 1.561
retrieving revision 1.562
diff -u -d -r1.561 -r1.562
--- tabular-data.html 13 Feb 2010 02:37:30 -0000 1.561
+++ tabular-data.html 14 Feb 2010 09:47:04 -0000 1.562
@@ -697,7 +697,8 @@
<code><a href="#the-tbody-element">tbody</a></code>, <code><a href="#the-tfoot-element">tfoot</a></code>, and <code><a href="#the-tr-element">tr</a></code>
elements.</dd>
<dt>Content model:</dt>
- <dd>Zero or more <code><a href="#the-col-element">col</a></code> elements.</dd>
+ <dd>If the <code title="attr-colgroup-span"><a href="#attr-colgroup-span">span</a></code> attribute is present: Empty.</dd>
+ <dd>If the <code title="attr-colgroup-span"><a href="#attr-colgroup-span">span</a></code> attribute is absent: Zero or more <code><a href="#the-col-element">col</a></code> elements.</dd>
<dt>Content attributes:</dt>
<dd><a href="elements.html#global-attributes">Global attributes</a></dd>
<dd><code title="attr-colgroup-span"><a href="#attr-colgroup-span">span</a></code></dd>
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.681
retrieving revision 1.682
diff -u -d -r1.681 -r1.682
--- Overview.html 14 Feb 2010 09:27:03 -0000 1.681
+++ Overview.html 14 Feb 2010 09:47:03 -0000 1.682
@@ -302,7 +302,7 @@
</dl><p>This specification is available in the following formats:
<a href="spec.html">single page HTML</a>,
<a href="Overview.html">multipage HTML</a>.
-This is revision 1.3772.
+This is revision 1.3774.
</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2009 <a href="http://www.w3.org/"><abbr title="World Wide
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.686
retrieving revision 1.687
diff -u -d -r1.686 -r1.687
--- spec.html 14 Feb 2010 09:27:03 -0000 1.686
+++ spec.html 14 Feb 2010 09:47:03 -0000 1.687
@@ -300,7 +300,7 @@
</dl><p>This specification is available in the following formats:
<a href=spec.html>single page HTML</a>,
<a href=Overview.html>multipage HTML</a>.
-This is revision 1.3772.
+This is revision 1.3774.
</p>
<p class=copyright><a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a>
© 2009 <a href=http://www.w3.org/><abbr title="World Wide
@@ -1388,10 +1388,13 @@
events, as in the DOM Events specifications. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used as
defined by the DOM Events specification. <!--
http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p><h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>The term <dfn id=plugin>plugin</dfn> is used to mean any content handler
- for Web content types that are either not supported by the user
- agent natively or that do not expose a DOM, which supports rendering
- the content as part of the user agent's interface.</p><p>Typically such content handlers are provided by third
- parties.</p><p class=example>One example of a plugin would be a PDF viewer
+ that supports displaying content as part of the user agent's
+ rendering of a <code>Document</code> object, but that neither acts
+ as a <a href=#child-browsing-context>child browsing context</a> of the
+ <code>Document</code> nor introduces any <code>Node</code> objects
+ to the <code>Document</code>'s DOM.</p><p>Typically such content handlers are provided by third parties,
+ though a user agent can designate content handlers to be
+ plugins.</p><p class=example>One example of a plugin would be a PDF viewer
that is instantiated in a <a href=#browsing-context>browsing context</a> when the
user navigates to a PDF file. This would count as a plugin
regardless of whether the party that implemented the PDF viewer
@@ -12127,7 +12130,8 @@
<code><a href=#the-tbody-element>tbody</a></code>, <code><a href=#the-tfoot-element>tfoot</a></code>, and <code><a href=#the-tr-element>tr</a></code>
elements.</dd>
<dt>Content model:</dt>
- <dd>Zero or more <code><a href=#the-col-element>col</a></code> elements.</dd>
+ <dd>If the <code title=attr-colgroup-span><a href=#attr-colgroup-span>span</a></code> attribute is present: Empty.</dd>
+ <dd>If the <code title=attr-colgroup-span><a href=#attr-colgroup-span>span</a></code> attribute is absent: Zero or more <code><a href=#the-col-element>col</a></code> elements.</dd>
<dt>Content attributes:</dt>
<dd><a href=#global-attributes>Global attributes</a></dd>
<dd><code title=attr-colgroup-span><a href=#attr-colgroup-span>span</a></code></dd>
Received on Sunday, 14 February 2010 09:47:08 UTC