Skip to content

Commit

Permalink
[e] (2) fix xrefs
Browse files Browse the repository at this point in the history 
git-svn-id: http://svn.whatwg.org/webapps@647 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Feb 28, 2007
1 parent 6f1e550 commit 3543685
Show file tree
Hide file tree
Showing 2 changed files with 37 additions and 36 deletions.
55 changes: 28 additions & 27 deletions index
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20928,7 +20928,7 @@ XXX selection ranges -->
<!-- introduced for <event-source> -->

<dd>Must be invoked whenever a <code title=event-message><a
href="#message0">message</a></code> event is targeted at or bubbles
href="#message">message</a></code> event is targeted at or bubbles
through the element.

<dt><dfn id=onmousedown
Expand Down Expand Up @@ -27077,15 +27077,15 @@ http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSPr

<p>Messages in <a href="#cross-document0">cross-document messaging</a> and,
by default, in <a href="#server-sent0">server-sent DOM events</a>, use the
<dfn id=message title=event-message>message</dfn> event.
<dfn id=message title=event-message><code>message</code></dfn> event.

<p>The following interface is defined for this event:

<pre class=idl>interface <dfn id=messageevent>MessageEvent</dfn> : Event {
readonly attribute DOMString <a href="#data6" title=dom-MessageEvent-data>data</a>;
readonly attribute DOMString <a href="#domain4" title=dom-MessageEvent-domain>domain</a>;
readonly attribute DOMString <a href="#uri0" title=dom-MessageEvent-uri>uri</a>;
readonly attribute Document <a href="#source2" title=dom-MessageEvent-source>source</a>;
readonly attribute DOMString <a href="#data4" title=dom-MessageEvent-data>data</a>;
readonly attribute DOMString <a href="#domain3" title=dom-MessageEvent-domain>domain</a>;
readonly attribute DOMString <a href="#uri" title=dom-MessageEvent-uri>uri</a>;
readonly attribute Document <a href="#source0" title=dom-MessageEvent-source>source</a>;
void <a href="#initmessageevent" title=dom-MessageEvent-initMessageEvent>initMessageEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString dataArg, in DOMString domainArg, in DOMString uriArg, in Document documentArg);
void <a href="#initmessageeventns" title=dom-MessageEvent-initMessageEventNS>initMessageEventNS</a>(in DOMString namespaceURI, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in DOMString dataArg, in DOMString domainArg, in DOMString uriArg, in Document documentArg);
};</pre>
Expand Down Expand Up @@ -27405,7 +27405,7 @@ Test:&nbsp;Line 2</pre>
<p>This field gives the name of the event. For example, <code
title="">load</code>, <code title="">DOMActivate</code>, <code
title="">updateTicker</code>. If there is no field with this name, the
name <code title=event-message><a href="#message0">message</a></code>
name <code title=event-message><a href="#message">message</a></code>
must be used.

<dt><code title="">Namespace</code> field
Expand Down Expand Up @@ -27448,7 +27448,7 @@ Test:&nbsp;Line 2</pre>

<p>If the <code title="">Namespace</code> is null and the <code
title="">Event</code> field is <code title=event-message><a
href="#message0">message</a></code> (including if it was not specified
href="#message">message</a></code> (including if it was not specified
explicitly), then the <code><a
href="#messageevent">MessageEvent</a></code> interface must be used.</p>

Expand Down Expand Up @@ -27611,11 +27611,11 @@ data: -2
data: 10</pre>

<p>...would cause an event <code title=event-message><a
href="#message0">message</a></code> with the interface <code><a
href="#message">message</a></code> with the interface <code><a
href="#messageevent">MessageEvent</a></code> to be dispatched on the
<code><a href="#event-source0">event-source</a></code> element, which
would then bubble up the DOM, and whose <code
title=dom-MessageEvent-data><a href="#data6">data</a></code> attribute
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>
again represents a newline).</p>

Expand All @@ -27634,18 +27634,18 @@ data: 10</pre>
<div class=example>
<p>The following stream contains four blocks and therefore fires four
events. The first block has just a comment, and will fire a <code
title=event-message><a href="#message0">message</a></code> event with all
title=event-message><a href="#message">message</a></code> event with all
the fields set to the empty string or null. The second block has two
fields with names "load" and "Target" respectively; since there is no
"<code title="">load</code>" member on the <code><a
href="#messageevent">MessageEvent</a></code> object that field is
ignored, leaving the event as a second <code title=event-message><a
href="#message0">message</a></code> event with all the fields set to the
href="#message">message</a></code> event with all the fields set to the
empty string or null, but this time the event is targetted at an element
with ID "image1". The third block is empty (no lines between two blank
lines), and the fourth block has only two comments, so they both yet
again fire <code title=event-message><a
href="#message0">message</a></code> events with all the fields set to the
href="#message">message</a></code> events with all the fields set to the
empty string or null.</p>

<pre>; test
Expand Down Expand Up @@ -28545,22 +28545,23 @@ Target: #image1
title="">message</var>)</code></dfn> method on a <code>Document</code>
object, the user agent must create an event that uses the <code><a
href="#messageevent">MessageEvent</a></code> interface, with the event
name <dfn id=message0 title=event-message><code>message</code></dfn>,
which bubbles, is cancelable, and has no default action. The <dfn id=data6
title=dom-MessageEvent-data><code>data</code></dfn> attribute must be set
to the value passed as the <var title="">message</var> argument to the
<code title=dom-document-postMessage><a
href="#postmessage">postMessage()</a></code> method, the <dfn id=domain4
title=dom-MessageEvent-domain><code>domain</code></dfn> attribute must be
set to the domain of the document that the script that invoked the methods
is associated with, the <dfn id=uri0
title=dom-MessageEvent-uri><code>uri</code></dfn> attribute must be set to
the URI of that document, and the <dfn id=source2
title=dom-MessageEvent-source><code>source</code></dfn> attribute must be
set to the <code>Document</code> object representing that document.
name <code title=event-message><a href="#message">message</a></code>,
which bubbles, is cancelable, and has no default action. The <code
title=dom-MessageEvent-data><a href="#data4">data</a></code> attribute
must be set to the value passed as the <var title="">message</var>
argument to the <code title=dom-document-postMessage><a
href="#postmessage">postMessage()</a></code> method, the <code
title=dom-MessageEvent-domain><a href="#domain3">domain</a></code>
attribute must be set to the domain of the document that the script that
invoked the methods is associated with, the <code
title=dom-MessageEvent-uri><a href="#uri">uri</a></code> attribute must be
set to the URI of that document, and the <code
title=dom-MessageEvent-source><a href="#source0">source</a></code>
attribute must be set to the <code>Document</code> object representing
that document.

<p class=warning>Authors should check the <code
title=dom-MessageEvent-domain><a href="#domain4">domain</a></code>
title=dom-MessageEvent-domain><a href="#domain3">domain</a></code>
attribute to ensure that messages are only accepted from domains that they
expect to receive messages from. Otherwise, bugs in the author's message
handling code could be exploited by hostile sites.
Expand Down
18 changes: 9 additions & 9 deletions source
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24811,7 +24811,7 @@ http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSPr

<p>Messages in <span>cross-document messaging</span> and, by
default, in <span>server-sent DOM events</span>, use the <dfn
title="event-message">message</dfn> event.</p>
title="event-message"><code>message</code></dfn> event.</p>

<p>The following interface is defined for this event:</p>

Expand Down Expand Up @@ -26315,18 +26315,18 @@ Target: #image1
title="">message</var>)</code></dfn> method on a
<code>Document</code> object, the user agent must create an event
that uses the <code>MessageEvent</code> interface, with the event
name <dfn title="event-message"><code>message</code></dfn>, which
bubbles, is cancelable, and has no default action. The <dfn
title="dom-MessageEvent-data"><code>data</code></dfn> attribute must
name <code title="event-message">message</code>, which
bubbles, is cancelable, and has no default action. The <code
title="dom-MessageEvent-data">data</code> attribute must
be set to the value passed as the <var title="">message</var>
argument to the <code
title="dom-document-postMessage">postMessage()</code> method, the
<dfn title="dom-MessageEvent-domain"><code>domain</code></dfn>
<code title="dom-MessageEvent-domain">domain</code>
attribute must be set to the domain of the document that the script
that invoked the methods is associated with, the <dfn
title="dom-MessageEvent-uri"><code>uri</code></dfn> attribute must
be set to the URI of that document, and the <dfn
title="dom-MessageEvent-source"><code>source</code></dfn> attribute
that invoked the methods is associated with, the <code
title="dom-MessageEvent-uri">uri</code> attribute must
be set to the URI of that document, and the <code
title="dom-MessageEvent-source">source</code> attribute
must be set to the <code>Document</code> object representing that
document.</p>

Expand Down

0 comments on commit 3543685

Please sign in to comment.