[html5] r1863 - [o] (2) Rename <event-source> to <eventsource> for consistency, while we sill can
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jul 11 02:40:40 PDT 2008
Author: ianh
Date: 2008-07-11 02:40:38 -0700 (Fri, 11 Jul 2008)
New Revision: 1863
Modified:
index
source
Log:
[o] (2) Rename <event-source> to <eventsource> for consistency, while we sill can
Modified: index
===================================================================
--- index 2008-07-11 09:35:00 UTC (rev 1862)
+++ index 2008-07-11 09:40:38 UTC (rev 1863)
@@ -928,8 +928,8 @@
<li><a href="#the-noscript"><span class=secno>4.10.2 </span>The
<code>noscript</code> element</a>
- <li><a href="#the-event-source"><span class=secno>4.10.3 </span>The
- <code>event-source</code> element</a>
+ <li><a href="#the-eventsource"><span class=secno>4.10.3 </span>The
+ <code>eventsource</code> element</a>
</ul>
<li><a href="#interactive-elements"><span class=secno>4.11
@@ -25518,8 +25518,8 @@
that will have <code title=dom-document-designMode><a
href="#designMode">designMode</a></code> enabled.
- <h4 id=the-event-source><span class=secno>4.10.3 </span>The <dfn
- id=event-source><code>event-source</code></dfn> element</h4>
+ <h4 id=the-eventsource><span class=secno>4.10.3 </span>The <dfn
+ id=eventsource><code>eventsource</code></dfn> element</h4>
<dl class=element>
<dt>Categories
@@ -25540,56 +25540,56 @@
<dt>Element-specific attributes:
- <dd><code title=attr-event-source-src><a href="#src11">src</a></code>
+ <dd><code title=attr-eventsource-src><a href="#src11">src</a></code>
<dt>DOM interface:
<dd>
<pre
class=idl>interface <dfn id=htmleventsourceelement>HTMLEventSourceElement</dfn> : <a href="#htmlelement">HTMLElement</a> {
- attribute DOMString <a href="#src12" title=dom-event-source-src>src</a>;
+ attribute DOMString <a href="#src12" title=dom-eventsource-src>src</a>;
};</pre>
</dl>
- <p>The <code><a href="#event-source">event-source</a></code> element
+ <p>The <code><a href="#eventsource">eventsource</a></code> element
represents a target for events generated by a remote server.
- <p>The <dfn id=src11 title=attr-event-source-src><code>src</code></dfn>
+ <p>The <dfn id=src11 title=attr-eventsource-src><code>src</code></dfn>
attribute, if specified, must give a <a href="#valid">valid URL</a>
identifying a resource that uses the <code>text/event-stream</code>
format.
- <p>When an <code><a href="#event-source">event-source</a></code> element
- with a <code title=attr-event-source-src><a href="#src11">src</a></code>
+ <p>When an <code><a href="#eventsource">eventsource</a></code> element with
+ a <code title=attr-eventsource-src><a href="#src11">src</a></code>
attribute specified is inserted into the document<!-- XXX xref -->, and
- when an <code><a href="#event-source">event-source</a></code> element that
+ when an <code><a href="#eventsource">eventsource</a></code> element that
is already in the document<!--XXX xref--> has a <code
- title=attr-event-source-src><a href="#src11">src</a></code> attribute
+ title=attr-eventsource-src><a href="#src11">src</a></code> attribute
added, the user agent must run the <a href="#add-declared">add declared
event source</a> algorithm.
- <p>While an <code><a href="#event-source">event-source</a></code> element
- is in a document<!--
+ <p>While an <code><a href="#eventsource">eventsource</a></code> element is
+ in a document<!--
XXX xref -->, if its <code
- title=attr-event-source-src><a href="#src11">src</a></code> attribute is
+ title=attr-eventsource-src><a href="#src11">src</a></code> attribute is
mutated, the user agent must must run the <a href="#remove1">remove
declared event source</a> algorithm followed by the <a
href="#add-declared">add declared event source</a> algorithm.
- <p>When an <code><a href="#event-source">event-source</a></code> element
- with a <code title=attr-event-source-src><a href="#src11">src</a></code>
+ <p>When an <code><a href="#eventsource">eventsource</a></code> element with
+ a <code title=attr-eventsource-src><a href="#src11">src</a></code>
attribute specified is removed from a document<!-- XXX xref -->, and when
- an <code><a href="#event-source">event-source</a></code> element that is
- in a document<!--XXX
- xref--> with a <code title=attr-event-source-src><a
+ an <code><a href="#eventsource">eventsource</a></code> element that is in
+ a document<!--XXX
+ xref--> with a <code title=attr-eventsource-src><a
href="#src11">src</a></code> attribute specified has its <code
- title=attr-event-source-src><a href="#src11">src</a></code> attribute
+ title=attr-eventsource-src><a href="#src11">src</a></code> attribute
removed, the user agent must run the <a href="#remove1">remove declared
event source</a> algorithm.</p>
<!-- changing the base URL doesn't trigger these algorithms -->
<p>When it is created, an <code><a
- href="#event-source">event-source</a></code> element must have its
+ href="#eventsource">eventsource</a></code> element must have its
<i>current declared event source</i> set to "undefined".
<p>The <dfn id=add-declared>add declared event source</dfn> algorithm is as
@@ -25598,8 +25598,8 @@
<ol>
<li><a href="#resolve" title="resolve a url">Resolve</a> the <a
href="#url">URL</a> specified by the <code><a
- href="#event-source">event-source</a></code> element's <code
- title=attr-event-source-src><a href="#src11">src</a></code> attribute.
+ href="#eventsource">eventsource</a></code> element's <code
+ title=attr-eventsource-src><a href="#src11">src</a></code> attribute.
<li>If that fails, then set the element's <i>current declared event
source</i> to "undefined" and abort these steps.
@@ -25607,8 +25607,8 @@
<li>Otherwise, act as if the <code
title=dom-remoteEventTarget-addEventSource><a
href="#addeventsource">addEventSource()</a></code> method on the <code><a
- href="#event-source">event-source</a></code> element had been invoked
- with the resulting <a href="#absolute">absolute URL</a>.
+ href="#eventsource">eventsource</a></code> element had been invoked with
+ the resulting <a href="#absolute">absolute URL</a>.
<li>Let the element's <i>current declared event source</i> be that <a
href="#absolute">absolute URL</a>.
@@ -25624,21 +25624,21 @@
<li>Otherwise, act as if the <code
title=dom-remoteEventTarget-removeEventSource><a
href="#removeeventsource">removeEventSource()</a></code> method on the
- <code><a href="#event-source">event-source</a></code> element had been
+ <code><a href="#eventsource">eventsource</a></code> element had been
invoked with the element's <i>current declared event source</i>.
<li>Let the element's <i>current declared event source</i> be "undefined".
</ol>
<p>There can be more than one <code><a
- href="#event-source">event-source</a></code> element per document, but
+ href="#eventsource">eventsource</a></code> element per document, but
authors should take care to avoid opening multiple connections to the same
server as HTTP recommends a limit to the number of simultaneous
connections that a user agent can open per server.</p>
<!-- XXX should we make 'load', 'error', 'abort' events fire on this
element? -->
- <p>The <dfn id=src12 title=dom-event-source-src><code>src</code></dfn> DOM
+ <p>The <dfn id=src12 title=dom-eventsource-src><code>src</code></dfn> DOM
attribute must <a href="#reflect">reflect</a> the content attribute of the
same name.
@@ -31373,7 +31373,7 @@
the element.
<dt><dfn id=onmessage title=handler-onmessage><code>onmessage</code></dfn></dt>
- <!-- introduced for <event-source> -->
+ <!-- introduced for <eventsource> -->
<dd>
<p>Must be invoked whenever a <code title=event-message><a
@@ -40803,11 +40803,11 @@
<h3 id=server-sent-events><span class=secno>7.2 </span><dfn
id=server-sent>Server-sent events</dfn></h3>
- <!-- event-source -->
+ <!-- eventsource -->
<p>This section describes a mechanism for allowing servers to dispatch DOM
events into documents that expect it. The <code><a
- href="#event-source">event-source</a></code> element provides a simple
+ href="#eventsource">eventsource</a></code> element provides a simple
interface to this mechanism.
<h4 id=the-remoteeventtarget><span class=secno>7.2.1 </span>The <code><a
@@ -40829,7 +40829,7 @@
href="#resolve" title="resolve a url">resolve</a> the <a
href="#url">URL</a> specified in <var title="">src</var>, and if that
succeeds, add the resulting <a href="#absolute">absolute URL</a> to the <a
- href="#list-of3" title=concept-event-source-list>list of event sources</a>
+ href="#list-of3" title=concept-eventsource-list>list of event sources</a>
for that object. The same URL can be registered multiple times. If the URL
fails to resolve, then the user agent must raise a <code>SYNTAX_ERR</code>
exception.
@@ -40840,7 +40840,7 @@
href="#resolve" title="resolve a url">resolve</a> the <a
href="#url">URL</a> specified in <var title="">src</var>, and if that
succeeds, remove the resulting <a href="#absolute">absolute URL</a> from
- the <a href="#list-of3" title=concept-event-source-list>list of event
+ the <a href="#list-of3" title=concept-eventsource-list>list of event
sources</a> for that object. If the same URI has been registered multiple
times, removing it must remove only one instance of that URI for each
invocation of the <code title=removeEventSource>removeEventSource()</code>
@@ -40851,7 +40851,7 @@
<p>Each object implementing the <code>EventTarget</code> and <code><a
href="#remoteeventtarget">RemoteEventTarget</a></code> interfaces has a
- <dfn id=list-of3 title=concept-event-source-list>list of event
+ <dfn id=list-of3 title=concept-eventsource-list>list of event
sources</dfn> that are registered for that object.
<p>When a new URI is added to this list, the user agent should, as soon as
@@ -41186,14 +41186,14 @@
<p>...would cause an event <code title=event-message><a
href="#message0">message</a></code> with the interface <code><a
href="#messageevent">MessageEvent</a></code> to be dispatched on the
- <code><a href="#event-source">event-source</a></code> element, whose
- <code title=dom-MessageEvent-data><a href="#data4">data</a></code>
- attribute would contain the string <code>YHOO\n-2\n10</code> (where
- <code>\n</code> represents a newline).</p>
+ <code><a href="#eventsource">eventsource</a></code> element, whose <code
+ title=dom-MessageEvent-data><a href="#data4">data</a></code> attribute
+ would contain the string <code>YHOO\n-2\n10</code> (where <code>\n</code>
+ represents a newline).</p>
<p>This could be used as follows:
- <pre><event-source src="http://stocks.example.com/ticker.php"
+ <pre><eventsource src="http://stocks.example.com/ticker.php"
onmessage="var data = event.data.split('\n'); updateStocks(data[0], data[1], data[2]);"></pre>
<p>...where <code title="">updateStocks()</code> is a function defined as:</p>
@@ -41270,17 +41270,16 @@
addresses can have multiple clients (due to sharing a proxy server). It is
better to include a unique identifier in the document when it is served
and then pass that identifier as part of the URL in the <code
- title=attr-event-source-src><a href="#src11">src</a></code> attribute of
- the <code><a href="#event-source">event-source</a></code> element.
+ title=attr-eventsource-src><a href="#src11">src</a></code> attribute of
+ the <code><a href="#eventsource">eventsource</a></code> element.
<p>Implementations that support HTTP's per-server connection limitation
might run into trouble when opening multiple pages from a site if each
- page has an <code><a href="#event-source">event-source</a></code> to the
+ page has an <code><a href="#eventsource">eventsource</a></code> to the
same domain. Authors can avoid this using the relatively complex mechanism
of using unique domain names per connection, or by allowing the user to
- enable or disable the <code><a
- href="#event-source">event-source</a></code> functionality on a per-page
- basis.
+ enable or disable the <code><a href="#eventsource">eventsource</a></code>
+ functionality on a per-page basis.
<h3 id=network><span class=secno>7.3 </span><dfn id=web-sockets>Web
sockets</dfn></h3>
@@ -42423,7 +42422,7 @@
<dd><code><a href="#base">base</a></code>, <code><a
href="#command0">command</a></code>, <code><a
- href="#event-source">event-source</a></code>, <code><a
+ href="#eventsource">eventsource</a></code>, <code><a
href="#link">link</a></code>, <code><a href="#meta0">meta</a></code>,
<code><a href="#hr">hr</a></code>, <code><a href="#br">br</a></code>,
<code><a href="#img">img</a></code>, <code><a
@@ -44115,7 +44114,7 @@
<code><a href="#dialog">dialog</a></code>, <code>dir</code>, <code><a
href="#div">div</a></code>, <code><a href="#dl">dl</a></code>, <code><a
href="#dt">dt</a></code>, <code><a href="#embed">embed</a></code>,
- <code><a href="#event-source">event-source</a></code>
+ <code><a href="#eventsource">eventsource</a></code>
<code>fieldset</code>, <code><a href="#figure">figure</a></code>,
<code><a href="#footer">footer</a></code>, <code>form</code>,
<code>frame</code>, <code>frameset</code>, <code><a
@@ -44176,7 +44175,7 @@
</dl>
<p class=big-issue>Still need to add these new elements to the lists:
- <code><a href="#event-source">event-source</a></code>, <code><a
+ <code><a href="#eventsource">eventsource</a></code>, <code><a
href="#section">section</a></code>, <code><a href="#nav">nav</a></code>,
<code><a href="#article">article</a></code>, <code><a
href="#aside">aside</a></code>, <code><a href="#header">header</a></code>,
@@ -47090,7 +47089,7 @@
<span>insertion mode</span>.</p>
<dt>A start tag whose tag name is one of: "base", "command",
- "event-source", "link"
+ "eventsource", "link"
<dd>
<p><a href="#insert0">Insert an HTML element</a> for the token.
@@ -47487,7 +47486,7 @@
attribute and its corresponding value to that element.</p>
<dt>A start tag token whose tag name is one of: "base", "command",
- "event-source", "link", "meta", "noframes", "script", "style", "title"
+ "eventsource", "link", "meta", "noframes", "script", "style", "title"
<dd>
<p>Process the token <a href="#using8">using the rules for</a> the "<a
@@ -48527,7 +48526,7 @@
"colgroup", "frame", "frameset", "head", "tbody", "td", "tfoot", "th",
"thead", "tr"</dt>
<!--<dt>An end tag whose tag name is one of: "area", "base",
- "basefont", "bgsound", "command", "embed", "event-source", "hr",
+ "basefont", "bgsound", "command", "embed", "eventsource", "hr",
"iframe", "image", "img", "input", "isindex", "link", "meta",
"noembed", "noframes", "param", "script", "select", "source",
"spacer", "style", "table", "textarea", "title", "wbr"</dt>-->
@@ -50067,7 +50066,7 @@
those "elements", more "macros", and thus we should never
serialize them -->
<!-- XXX when we get around to it, add
- event-source -->
+ eventsource -->
<p>If <var title="">current node</var> is a <code><a
href="#pre">pre</a></code> <code>textarea</code>, or
<code>listing</code> element, append a U+000A LINE FEED (LF)
Modified: source
===================================================================
--- source 2008-07-11 09:35:00 UTC (rev 1862)
+++ source 2008-07-11 09:40:38 UTC (rev 1863)
@@ -23213,7 +23213,7 @@
title="dom-document-designMode">designMode</code> enabled.</p>
- <h4>The <dfn><code>event-source</code></dfn> element</h4>
+ <h4>The <dfn><code>eventsource</code></dfn> element</h4>
<dl class="element">
<dt>Categories</dt>
@@ -23225,51 +23225,51 @@
<dt>Content model:</dt>
<dd>Empty.</dd>
<dt>Element-specific attributes:</dt>
- <dd><code title="attr-event-source-src">src</code></dd>
+ <dd><code title="attr-eventsource-src">src</code></dd>
<dt>DOM interface:</dt>
<dd>
<pre class="idl">interface <dfn>HTMLEventSourceElement</dfn> : <span>HTMLElement</span> {
- attribute DOMString <span title="dom-event-source-src">src</span>;
+ attribute DOMString <span title="dom-eventsource-src">src</span>;
};</pre>
</dd>
</dl>
- <p>The <code>event-source</code> element represents a target for
+ <p>The <code>eventsource</code> element represents a target for
events generated by a remote server.</p>
- <p>The <dfn title="attr-event-source-src"><code>src</code></dfn>
+ <p>The <dfn title="attr-eventsource-src"><code>src</code></dfn>
attribute, if specified, must give a <span>valid URL</span>
identifying a resource that uses the <code>text/event-stream</code>
format.</p>
- <p>When an <code>event-source</code> element with a <code
- title="attr-event-source-src">src</code> attribute specified is
+ <p>When an <code>eventsource</code> element with a <code
+ title="attr-eventsource-src">src</code> attribute specified is
inserted into the document<!-- XXX xref -->, and when an
- <code>event-source</code> element that is already in the
+ <code>eventsource</code> element that is already in the
document<!--XXX xref--> has a <code
- title="attr-event-source-src">src</code> attribute added, the user
+ title="attr-eventsource-src">src</code> attribute added, the user
agent must run the <span>add declared event source</span>
algorithm.</p>
- <p>While an <code>event-source</code> element is in a document<!--
- XXX xref -->, if its <code title="attr-event-source-src">src</code>
+ <p>While an <code>eventsource</code> element is in a document<!--
+ XXX xref -->, if its <code title="attr-eventsource-src">src</code>
attribute is mutated, the user agent must must run the <span>remove
declared event source</span> algorithm followed by the <span>add
declared event source</span> algorithm.</p>
- <p>When an <code>event-source</code> element with a <code
- title="attr-event-source-src">src</code> attribute specified is
+ <p>When an <code>eventsource</code> element with a <code
+ title="attr-eventsource-src">src</code> attribute specified is
removed from a document<!-- XXX xref -->, and when an
- <code>event-source</code> element that is in a document<!--XXX
- xref--> with a <code title="attr-event-source-src">src</code>
+ <code>eventsource</code> element that is in a document<!--XXX
+ xref--> with a <code title="attr-eventsource-src">src</code>
attribute specified has its <code
- title="attr-event-source-src">src</code> attribute removed, the user
+ title="attr-eventsource-src">src</code> attribute removed, the user
agent must run the <span>remove declared event source</span>
algorithm.</p>
<!-- changing the base URL doesn't trigger these algorithms -->
- <p>When it is created, an <code>event-source</code> element must
+ <p>When it is created, an <code>eventsource</code> element must
have its <i>current declared event source</i> set to
"undefined".</p>
@@ -23279,15 +23279,15 @@
<ol>
<li><span title="resolve a url">Resolve</span> the <span>URL</span>
- specified by the <code>event-source</code> element's <code
- title="attr-event-source-src">src</code> attribute.</li>
+ specified by the <code>eventsource</code> element's <code
+ title="attr-eventsource-src">src</code> attribute.</li>
<li>If that fails, then set the element's <i>current declared event
source</i> to "undefined" and abort these steps.</li>
<li>Otherwise, act as if the <code
title="dom-remoteEventTarget-addEventSource">addEventSource()</code>
- method on the <code>event-source</code> element had been invoked
+ method on the <code>eventsource</code> element had been invoked
with the resulting <span>absolute URL</span>.</li>
<li>Let the element's <i>current declared event source</i> be that
@@ -23305,7 +23305,7 @@
<li>Otherwise, act as if the <code
title="dom-remoteEventTarget-removeEventSource">removeEventSource()</code>
- method on the <code>event-source</code> element had been invoked
+ method on the <code>eventsource</code> element had been invoked
with the element's <i>current declared event source</i>.</li>
<li>Let the element's <i>current declared event source</i> be
@@ -23313,7 +23313,7 @@
</ol>
- <p>There can be more than one <code>event-source</code> element per
+ <p>There can be more than one <code>eventsource</code> element per
document, but authors should take care to avoid opening multiple
connections to the same server as HTTP recommends a limit to the
number of simultaneous connections that a user agent can open per
@@ -23322,7 +23322,7 @@
<!-- XXX should we make 'load', 'error', 'abort' events fire on this
element? -->
- <p>The <dfn title="dom-event-source-src"><code>src</code></dfn> DOM
+ <p>The <dfn title="dom-eventsource-src"><code>src</code></dfn> DOM
attribute must <span>reflect</span> the content attribute of the
same name.</p>
@@ -28918,7 +28918,7 @@
title="event-load">load</code> event is targeted at or bubbles
through the element.</p></dd>
- <dt><dfn title="handler-onmessage"><code>onmessage</code></dfn></dt> <!-- introduced for <event-source> -->
+ <dt><dfn title="handler-onmessage"><code>onmessage</code></dfn></dt> <!-- introduced for <eventsource> -->
<dd><p>Must be invoked whenever a <code
title="event-message">message</code> event is targeted at or bubbles
@@ -38343,11 +38343,11 @@
<h3 id="server-sent-events"><dfn>Server-sent events</dfn></h3>
- <!-- event-source -->
+ <!-- eventsource -->
<p>This section describes a mechanism for allowing servers to
dispatch DOM events into documents that expect it. The
- <code>event-source</code> element provides a simple interface to
+ <code>eventsource</code> element provides a simple interface to
this mechanism.</p>
@@ -38368,7 +38368,7 @@
title="">src</var>)</code></dfn> method is invoked, the user agent
must <span title="resolve a url">resolve</span> the <span>URL</span>
specified in <var title="">src</var>, and if that succeeds, add the resulting <span>absolute URL</span>
- to the <span title="concept-event-source-list">list of event
+ to the <span title="concept-eventsource-list">list of event
sources</span> for that object. The same URL can be registered
multiple times. If the URL fails to resolve, then the user agent
must raise a <code>SYNTAX_ERR</code> exception.</p>
@@ -38379,7 +38379,7 @@
must <span title="resolve a url">resolve</span> the <span>URL</span>
specified in <var title="">src</var>, and if that succeeds, remove
the resulting <span>absolute URL</span> from the <span
- title="concept-event-source-list">list of event sources</span> for
+ title="concept-eventsource-list">list of event sources</span> for
that object. If the same URI has been registered multiple times,
removing it must remove only one instance of that URI for each
invocation of the <code
@@ -38391,7 +38391,7 @@
<p>Each object implementing the <code>EventTarget</code> and
<code>RemoteEventTarget</code> interfaces has a <dfn
- title="concept-event-source-list">list of event sources</dfn> that
+ title="concept-eventsource-list">list of event sources</dfn> that
are registered for that object.</p>
<p>When a new URI is added to this list, the user agent should, as
@@ -38751,13 +38751,13 @@
<p>...would cause an event <code
title="event-message">message</code> with the interface
<code>MessageEvent</code> to be dispatched on the
- <code>event-source</code> element, whose <code
+ <code>eventsource</code> element, whose <code
title="dom-MessageEvent-data">data</code> attribute would contain
the string <code>YHOO\n-2\n10</code> (where <code>\n</code>
represents a newline).</p>
<p>This could be used as follows:
- <pre><event-source src="http://stocks.example.com/ticker.php"
+ <pre><eventsource src="http://stocks.example.com/ticker.php"
onmessage="var data = event.data.split('\n'); updateStocks(data[0], data[1], data[2]);"></pre>
<p>...where <code title="">updateStocks()</code> is a function defined as:</p>
<pre>function updateStocks(symbol, delta, value) { ... }</pre>
@@ -38839,15 +38839,15 @@
individual IP addresses can have multiple clients (due to sharing a
proxy server). It is better to include a unique identifier in the
document when it is served and then pass that identifier as part of
- the URL in the <code title="attr-event-source-src">src</code>
- attribute of the <code>event-source</code> element.</p>
+ the URL in the <code title="attr-eventsource-src">src</code>
+ attribute of the <code>eventsource</code> element.</p>
<p>Implementations that support HTTP's per-server connection
limitation might run into trouble when opening multiple pages from a
- site if each page has an <code>event-source</code> to the same
+ site if each page has an <code>eventsource</code> to the same
domain. Authors can avoid this using the relatively complex
mechanism of using unique domain names per connection, or by
- allowing the user to enable or disable the <code>event-source</code>
+ allowing the user to enable or disable the <code>eventsource</code>
functionality on a per-page basis.</p>
@@ -40100,7 +40100,7 @@
<dt><dfn>Void elements</dfn></dt>
<dd><code>base</code>, <code>command</code>,
- <code>event-source</code>, <code>link</code>, <code>meta</code>,
+ <code>eventsource</code>, <code>link</code>, <code>meta</code>,
<code>hr</code>, <code>br</code>, <code>img</code>,
<code>embed</code>, <code>param</code>, <code>area</code>,
<code>col</code>, <code>input</code>, <code>source</code></dd>
@@ -41777,7 +41777,7 @@
<code>command</code>, <code>datagrid</code>, <code>dd</code>,
<code>details</code>, <code>dialog</code>, <code>dir</code>,
<code>div</code>, <code>dl</code>, <code>dt</code>,
- <code>embed</code>, <code>event-source</code>
+ <code>embed</code>, <code>eventsource</code>
<code>fieldset</code>, <code>figure</code>, <code>footer</code>,
<code>form</code>, <code>frame</code>, <code>frameset</code>,
<code>h1</code>, <code>h2</code>, <code>h3</code>, <code>h4</code>,
@@ -41820,7 +41820,7 @@
</dl>
<p class="big-issue">Still need to add these new elements to the
- lists: <code>event-source</code>, <code>section</code>,
+ lists: <code>eventsource</code>, <code>section</code>,
<code>nav</code>, <code>article</code>, <code>aside</code>,
<code>header</code>, <code>footer</code>, <code>datagrid</code>,
<code>command</code></p>
@@ -44283,7 +44283,7 @@
</dd>
<dt>A start tag whose tag name is one of: "base", "command",
- "event-source", "link"</dt>
+ "eventsource", "link"</dt>
<dd>
<p><span>Insert an HTML element</span> for the token. Immediately
@@ -44704,7 +44704,7 @@
</dd>
<dt>A start tag token whose tag name is one of: "base", "command",
- "event-source", "link", "meta", "noframes", "script", "style",
+ "eventsource", "link", "meta", "noframes", "script", "style",
"title"</dt>
<dd>
<p>Process the token <span>using the rules for</span> the "<span
@@ -45805,7 +45805,7 @@
"col", "colgroup", "frame", "frameset", "head", "tbody", "td",
"tfoot", "th", "thead", "tr"</dt>
<!--<dt>An end tag whose tag name is one of: "area", "base",
- "basefont", "bgsound", "command", "embed", "event-source", "hr",
+ "basefont", "bgsound", "command", "embed", "eventsource", "hr",
"iframe", "image", "img", "input", "isindex", "link", "meta",
"noembed", "noframes", "param", "script", "select", "source",
"spacer", "style", "table", "textarea", "title", "wbr"</dt>--> <!--
@@ -47400,7 +47400,7 @@
and keygen, but we don't list those because we don't consider
those "elements", more "macros", and thus we should never
serialize them --> <!-- XXX when we get around to it, add
- event-source -->
+ eventsource -->
<p>If <var title="">current node</var> is a <code>pre</code>
<code>textarea</code>, or <code>listing</code> element, append
More information about the Commit-Watchers
mailing list