Skip to content
Permalink
Browse files
[e] (0) Move slightly more towards using the word 'type' rather than …
…'name' for the concept of an event name

Affected topics: DOM APIs, Server-Sent Events, WebSocket API

git-svn-id: http://svn.whatwg.org/webapps@7099 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed May 8, 2012
1 parent 090bcc1 commit e090325bbd9262a34d4464f8ad0b384ba0182933
Showing with 42 additions and 32 deletions.
  1. +13 −11 complete.html
  2. +13 −11 index
  3. +16 −10 source
@@ -3941,7 +3941,10 @@ <h4 id=dependencies><span class=secno>2.2.2 </span>Dependencies</h4>

<li><dfn id=event-click title=event-click><code>click</code></dfn> event</li>

</ul><p>In addition, user agents must implement the features defined in
</ul><p>This specification sometimes uses the term <dfn title="">name</dfn> to refer to the event's <code title=dom-event-type>type</code>; as in, "an event named <code title="">click</code>" or "if the event name is <code title="">keypress</code>". The terms "name" and "type" for events
are synonymous.</p>

<p>In addition, user agents must implement the features defined in
the DOM Parsing and Serialization specification, HTML
Editing APIs, and UndoManager and DOM Transaction specifications
that apply to their conformance class.
@@ -80288,7 +80291,6 @@ <h4 id=server-sent-events-intro><span class=secno>10.2.1 </span>Introduction</h4
data: 2153

event: add

data: 113411</pre>

<p>The script to handle such a stream would look like this (where
@@ -80663,7 +80665,7 @@ <h4 id=event-stream-interpretation><span class=secno>10.2.5 </span>Interpreting
a line can end.</p>

<p>When a stream is parsed, a <var title="">data</var> buffer, an
<var title="">event name</var> buffer, and a <var title="">last
<var title="">event type</var> buffer, and a <var title="">last
event ID</var> buffer must be associated with it. They must be
initialized to the empty string</p>

@@ -80722,7 +80724,7 @@ <h4 id=event-stream-interpretation><span class=secno>10.2.5 </span>Interpreting

<dl class=switch><dt>If the field name is "event"</dt>

<dd><p>Set the <var title="">event name</var> buffer to field
<dd><p>Set the <var title="">event type</var> buffer to field
value.</dd>


@@ -80798,7 +80800,7 @@ <h4 id=event-stream-interpretation><span class=secno>10.2.5 </span>Interpreting
from the <var title="">data</var> buffer.</li>

<li><p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code>
interface, with the event name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is not
interface, with the event type <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is not
cancelable, and has no default action. The <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute must be
initialized to the value of the <var title="">data</var> buffer,
the <code title=dom-MessageEvent-origin><a href=#dom-messageevent-origin>origin</a></code> attribute
@@ -80809,12 +80811,12 @@ <h4 id=event-stream-interpretation><span class=secno>10.2.5 </span>Interpreting
attribute must be initialized to the <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID
string</a> of the event source.</li>

<li><p>If the <var title="">event name</var> buffer has a value
<li><p>If the <var title="">event type</var> buffer has a value
other than the empty string, change the <a href=#concept-event-type title=concept-event-type>type</a> of the newly created event
to equal the value of the <var title="">event name</var>
to equal the value of the <var title="">event type</var>
buffer.</li>

<li><p>Set the <var title="">data</var> buffer and the <var title="">event name</var> buffer to the empty string.</li>
<li><p>Set the <var title="">data</var> buffer and the <var title="">event type</var> buffer to the empty string.</li>

<li><p><a href=#queue-a-task>Queue a task</a> which, if the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute is
set to a value other than <code title=dom-EventSource-CLOSED><a href=#dom-eventsource-closed>CLOSED</a></code>, dispatches the newly
@@ -81656,7 +81658,7 @@ <h4 id=the-websocket-interface><span class=secno>10.3.2 </span>The <code><a href
<li>

<p>Let <var title="">event</var> be an event that uses the
<code><a href=#messageevent>MessageEvent</a></code> interface, with the event name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
<code><a href=#messageevent>MessageEvent</a></code> interface, with the event type <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
not cancelable, and has no default action.
</p>

@@ -81744,7 +81746,7 @@ <h4 id=the-websocket-interface><span class=secno>10.3.2 </span>The <code><a href
at the <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>

<li><p>Create an event that uses the <code><a href=#closeevent>CloseEvent</a></code>
interface, with the event name <code title=event-close>close</code>, which does not bubble, is not
interface, with the event type <code title=event-close>close</code>, which does not bubble, is not
cancelable, has no default action, whose <code title=dom-CloseEvent-wasClean><a href=#dom-closeevent-wasclean>wasClean</a></code> attribute is initialized to
true if the connection closed <i title="">cleanly</i> and false
otherwise, whose <code title=dom-CloseEvent-code><a href=#dom-closeevent-code>code</a></code>
@@ -82237,7 +82239,7 @@ <h4 id=posting-messages><span class=secno>10.4.3 </span>Posting messages</h4>
<li>

<p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code>
interface, with the event name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
interface, with the event type <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
not cancelable, and has no default action. The <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute must be
initialized to the value of <var title="">message clone</var>, the
<code title=dom-MessageEvent-origin><a href=#dom-messageevent-origin>origin</a></code> attribute must
24 index
@@ -3941,7 +3941,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

<li><dfn id=event-click title=event-click><code>click</code></dfn> event</li>

</ul><p>In addition, user agents must implement the features defined in
</ul><p>This specification sometimes uses the term <dfn title="">name</dfn> to refer to the event's <code title=dom-event-type>type</code>; as in, "an event named <code title="">click</code>" or "if the event name is <code title="">keypress</code>". The terms "name" and "type" for events
are synonymous.</p>

<p>In addition, user agents must implement the features defined in
the DOM Parsing and Serialization specification, HTML
Editing APIs, and UndoManager and DOM Transaction specifications
that apply to their conformance class.
@@ -80288,7 +80291,6 @@ event: remove
data: 2153

event: add

data: 113411</pre>

<p>The script to handle such a stream would look like this (where
@@ -80663,7 +80665,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF
a line can end.</p>

<p>When a stream is parsed, a <var title="">data</var> buffer, an
<var title="">event name</var> buffer, and a <var title="">last
<var title="">event type</var> buffer, and a <var title="">last
event ID</var> buffer must be associated with it. They must be
initialized to the empty string</p>

@@ -80722,7 +80724,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF

<dl class=switch><dt>If the field name is "event"</dt>

<dd><p>Set the <var title="">event name</var> buffer to field
<dd><p>Set the <var title="">event type</var> buffer to field
value.</dd>


@@ -80798,7 +80800,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF
from the <var title="">data</var> buffer.</li>

<li><p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code>
interface, with the event name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is not
interface, with the event type <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is not
cancelable, and has no default action. The <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute must be
initialized to the value of the <var title="">data</var> buffer,
the <code title=dom-MessageEvent-origin><a href=#dom-messageevent-origin>origin</a></code> attribute
@@ -80809,12 +80811,12 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF
attribute must be initialized to the <a href=#concept-event-stream-last-event-id title=concept-event-stream-last-event-id>last event ID
string</a> of the event source.</li>

<li><p>If the <var title="">event name</var> buffer has a value
<li><p>If the <var title="">event type</var> buffer has a value
other than the empty string, change the <a href=#concept-event-type title=concept-event-type>type</a> of the newly created event
to equal the value of the <var title="">event name</var>
to equal the value of the <var title="">event type</var>
buffer.</li>

<li><p>Set the <var title="">data</var> buffer and the <var title="">event name</var> buffer to the empty string.</li>
<li><p>Set the <var title="">data</var> buffer and the <var title="">event type</var> buffer to the empty string.</li>

<li><p><a href=#queue-a-task>Queue a task</a> which, if the <code title=dom-EventSource-readyState><a href=#dom-eventsource-readystate>readyState</a></code> attribute is
set to a value other than <code title=dom-EventSource-CLOSED><a href=#dom-eventsource-closed>CLOSED</a></code>, dispatches the newly
@@ -81656,7 +81658,7 @@ socket.onopen = function () {
<li>

<p>Let <var title="">event</var> be an event that uses the
<code><a href=#messageevent>MessageEvent</a></code> interface, with the event name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
<code><a href=#messageevent>MessageEvent</a></code> interface, with the event type <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
not cancelable, and has no default action.
</p>

@@ -81744,7 +81746,7 @@ socket.onopen = function () {
at the <code><a href=#websocket>WebSocket</a></code> object. <a href=#refsWSP>[WSP]</a></li>

<li><p>Create an event that uses the <code><a href=#closeevent>CloseEvent</a></code>
interface, with the event name <code title=event-close>close</code>, which does not bubble, is not
interface, with the event type <code title=event-close>close</code>, which does not bubble, is not
cancelable, has no default action, whose <code title=dom-CloseEvent-wasClean><a href=#dom-closeevent-wasclean>wasClean</a></code> attribute is initialized to
true if the connection closed <i title="">cleanly</i> and false
otherwise, whose <code title=dom-CloseEvent-code><a href=#dom-closeevent-code>code</a></code>
@@ -82237,7 +82239,7 @@ function receiver(e) {
<li>

<p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code>
interface, with the event name <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
interface, with the event type <code title=event-message><a href=#event-message>message</a></code>, which does not bubble, is
not cancelable, and has no default action. The <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute must be
initialized to the value of <var title="">message clone</var>, the
<code title=dom-MessageEvent-origin><a href=#dom-messageevent-origin>origin</a></code> attribute must
26 source
@@ -2884,6 +2884,13 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

</ul>

<p>This specification sometimes uses the term <dfn
title="">name</dfn> to refer to the event's <code
title="dom-event-type">type</code>; as in, "an event named <code
title="">click</code>" or "if the event name is <code
title="">keypress</code>". The terms "name" and "type" for events
are synonymous.</p>

<p>In addition, user agents must implement the features defined in
the DOM Parsing and Serialization specification, HTML
Editing APIs, and UndoManager and DOM Transaction specifications
@@ -93277,7 +93284,6 @@ event: remove
data: 2153

event: add

data: 113411</pre>

<p>The script to handle such a stream would look like this (where
@@ -93739,7 +93745,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF
a line can end.</p>

<p>When a stream is parsed, a <var title="">data</var> buffer, an
<var title="">event name</var> buffer, and a <var title="">last
<var title="">event type</var> buffer, and a <var title="">last
event ID</var> buffer must be associated with it. They must be
initialized to the empty string</p>

@@ -93806,7 +93812,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF

<dt>If the field name is "event"</dt>

<dd><p>Set the <var title="">event name</var> buffer to field
<dd><p>Set the <var title="">event type</var> buffer to field
value.</p></dd>


@@ -93890,7 +93896,7 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF
from the <var title="">data</var> buffer.</p></li>

<li><p>Create an event that uses the <code>MessageEvent</code>
interface, with the event name <code
interface, with the event type <code
title="event-message">message</code>, which does not bubble, is not
cancelable, and has no default action. The <code
title="dom-MessageEvent-data">data</code> attribute must be
@@ -93904,14 +93910,14 @@ any-char = %x0000-0009 / %x000B-000C / %x000E-10FFFF
title="concept-event-stream-last-event-id">last event ID
string</span> of the event source.</p></li>

<li><p>If the <var title="">event name</var> buffer has a value
<li><p>If the <var title="">event type</var> buffer has a value
other than the empty string, change the <span
title="concept-event-type">type</span> of the newly created event
to equal the value of the <var title="">event name</var>
to equal the value of the <var title="">event type</var>
buffer.</p></li>

<li><p>Set the <var title="">data</var> buffer and the <var
title="">event name</var> buffer to the empty string.</p></li>
title="">event type</var> buffer to the empty string.</p></li>

<li><p><span>Queue a task</span> which, if the <code
title="dom-EventSource-readyState">readyState</code> attribute is
@@ -94921,7 +94927,7 @@ socket.onopen = function () {
<li>

<p>Let <var title="">event</var> be an event that uses the
<code>MessageEvent</code> interface, with the event name <code
<code>MessageEvent</code> interface, with the event type <code
title="event-message">message</code>, which does not bubble, is
not cancelable, and has no default action.
<!--END complete-->
@@ -95040,7 +95046,7 @@ socket.onopen = function () {
href="#refsWSP">[WSP]</a></p></li>

<li><p>Create an event that uses the <code>CloseEvent</code>
interface, with the event name <code
interface, with the event type <code
title="event-close">close</code>, which does not bubble, is not
cancelable, has no default action, whose <code
title="dom-CloseEvent-wasClean">wasClean</code> attribute is initialized to
@@ -95623,7 +95629,7 @@ function receiver(e) {
<li>

<p>Create an event that uses the <code>MessageEvent</code>
interface, with the event name <code
interface, with the event type <code
title="event-message">message</code>, which does not bubble, is
not cancelable, and has no default action. The <code
title="dom-MessageEvent-data">data</code> attribute must be

0 comments on commit e090325

Please sign in to comment.