Skip to content

Commit

Permalink
[giow] (0) Use 'message' instead of 'text' for the event name for con…
Browse files Browse the repository at this point in the history
…sistency with other parts of the platform.

git-svn-id: http://svn.whatwg.org/webapps@5951 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Mar 14, 2011
1 parent 2f52126 commit ecc4f8d
Show file tree
Hide file tree
Showing 3 changed files with 12 additions and 12 deletions.
8 changes: 4 additions & 4 deletions complete.html
Expand Up @@ -71716,7 +71716,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec

// <span class=XXX>connection quality information</span>

attribute <a href=#function>Function</a> <a href=#handler-peerconnection-ontext title=handler-PeerConnection-ontext>ontext</a>;
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onmessage title=handler-PeerConnection-onmessage>onmessage</a>;
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream>onaddstream</a>;
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream>onremovestream</a>;
};
Expand Down Expand Up @@ -71810,7 +71810,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
every message will be received.</p>

<p>When a message sent in this manner from the other peer is
received, a <code title=event-PeerConnection-text>text</code>
received, a <code title=event-PeerConnection-message>message</code>
event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>

</dd>
Expand Down Expand Up @@ -72202,7 +72202,7 @@ <h3 id=peer-to-peer-connections><span class=secno>9.4 </span>Peer-to-peer connec
interface:</p>

<table><thead><tr><th><a href=#event-handlers title="event handlers">Event handler</a> <th><a href=#event-handler-event-type>Event handler event type</a>
<tbody><tr><td><dfn id=handler-peerconnection-ontext title=handler-PeerConnection-ontext><code>ontext</code></dfn> <td> <code title=event-stream-text>text</code>
<tbody><tr><td><dfn id=handler-peerconnection-onmessage title=handler-PeerConnection-onmessage><code>onmessage</code></dfn> <td> <code title=event-stream-message>message</code>
<tr><td><dfn id=handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream><code>onaddstream</code></dfn> <td> <code title=event-stream-addstream>addstream</code>
<tr><td><dfn id=handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream><code>onremovestream</code></dfn> <td> <code title=event-stream-removestream>removestream</code>
</table><hr><p>The <a href=#task-source>task source</a> for the <a href=#concept-task title=concept-task>tasks</a> listed in this section is the
Expand Down Expand Up @@ -72390,7 +72390,7 @@ <h3 id=the-data-stream><span class=secno>9.5 </span>The data stream</h3>
handling</a>.</li>

<li><p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code>
interface, with the name <code title=event-text>text</code>,
interface, with the name <code title=event-message><a href=#event-message>message</a></code>,
which does not bubble, is not cancelable, has no default action,
and has a <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute
whose value is <var title="">message</var>, and <a href=#queue-a-task>queue a
Expand Down
8 changes: 4 additions & 4 deletions index
Expand Up @@ -71725,7 +71725,7 @@ interface <dfn id=peerconnection>PeerConnection</dfn> {

// <span class=XXX>connection quality information</span>

attribute <a href=#function>Function</a> <a href=#handler-peerconnection-ontext title=handler-PeerConnection-ontext>ontext</a>;
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onmessage title=handler-PeerConnection-onmessage>onmessage</a>;
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream>onaddstream</a>;
attribute <a href=#function>Function</a> <a href=#handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream>onremovestream</a>;
};
Expand Down Expand Up @@ -71819,7 +71819,7 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {
every message will be received.</p>

<p>When a message sent in this manner from the other peer is
received, a <code title=event-PeerConnection-text>text</code>
received, a <code title=event-PeerConnection-message>message</code>
event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>

</dd>
Expand Down Expand Up @@ -72211,7 +72211,7 @@ interface <dfn id=signalingcallback>SignalingCallback</dfn> {
interface:</p>

<table><thead><tr><th><a href=#event-handlers title="event handlers">Event handler</a> <th><a href=#event-handler-event-type>Event handler event type</a>
<tbody><tr><td><dfn id=handler-peerconnection-ontext title=handler-PeerConnection-ontext><code>ontext</code></dfn> <td> <code title=event-stream-text>text</code>
<tbody><tr><td><dfn id=handler-peerconnection-onmessage title=handler-PeerConnection-onmessage><code>onmessage</code></dfn> <td> <code title=event-stream-message>message</code>
<tr><td><dfn id=handler-peerconnection-onaddstream title=handler-PeerConnection-onaddstream><code>onaddstream</code></dfn> <td> <code title=event-stream-addstream>addstream</code>
<tr><td><dfn id=handler-peerconnection-onremovestream title=handler-PeerConnection-onremovestream><code>onremovestream</code></dfn> <td> <code title=event-stream-removestream>removestream</code>
</table><hr><p>The <a href=#task-source>task source</a> for the <a href=#concept-task title=concept-task>tasks</a> listed in this section is the
Expand Down Expand Up @@ -72399,7 +72399,7 @@ local.onaddstream = function (event) {
handling</a>.</li>

<li><p>Create an event that uses the <code><a href=#messageevent>MessageEvent</a></code>
interface, with the name <code title=event-text>text</code>,
interface, with the name <code title=event-message><a href=#event-message>message</a></code>,
which does not bubble, is not cancelable, has no default action,
and has a <code title=dom-MessageEvent-data><a href=#dom-messageevent-data>data</a></code> attribute
whose value is <var title="">message</var>, and <a href=#queue-a-task>queue a
Expand Down
8 changes: 4 additions & 4 deletions source
Expand Up @@ -81815,7 +81815,7 @@ interface <dfn>PeerConnection</dfn> {

// <span class="XXX">connection quality information</span>

attribute <span>Function</span> <span title="handler-PeerConnection-ontext">ontext</span>;
attribute <span>Function</span> <span title="handler-PeerConnection-onmessage">onmessage</span>;
attribute <span>Function</span> <span title="handler-PeerConnection-onaddstream">onaddstream</span>;
attribute <span>Function</span> <span title="handler-PeerConnection-onremovestream">onremovestream</span>;
};
Expand Down Expand Up @@ -81922,7 +81922,7 @@ interface <dfn>SignalingCallback</dfn> {
every message will be received.</p>

<p>When a message sent in this manner from the other peer is
received, a <code title="event-PeerConnection-text">text</code>
received, a <code title="event-PeerConnection-message">message</code>
event is dispatched at the <code>PeerConnection</code> object.</p>

</dd>
Expand Down Expand Up @@ -82407,7 +82407,7 @@ interface <dfn>SignalingCallback</dfn> {
<thead>
<tr><th><span title="event handlers">Event handler</span> <th><span>Event handler event type</span>
<tbody>
<tr><td><dfn title="handler-PeerConnection-ontext"><code>ontext</code></dfn> <td> <code title="event-stream-text">text</code>
<tr><td><dfn title="handler-PeerConnection-onmessage"><code>onmessage</code></dfn> <td> <code title="event-stream-message">message</code>
<tr><td><dfn title="handler-PeerConnection-onaddstream"><code>onaddstream</code></dfn> <td> <code title="event-stream-addstream">addstream</code>
<tr><td><dfn title="handler-PeerConnection-onremovestream"><code>onremovestream</code></dfn> <td> <code title="event-stream-removestream">removestream</code>
</table>
Expand Down Expand Up @@ -82622,7 +82622,7 @@ local.onaddstream = function (event) {
handling</span>.</p></li>

<li><p>Create an event that uses the <code>MessageEvent</code>
interface, with the name <code title="event-text">text</code>,
interface, with the name <code title="event-message">message</code>,
which does not bubble, is not cancelable, has no default action,
and has a <code title="dom-MessageEvent-data">data</code> attribute
whose value is <var title="">message</var>, and <span>queue a
Expand Down

0 comments on commit ecc4f8d

Please sign in to comment.