Skip to content

Commit

Permalink
[e] (0) xref
Browse files Browse the repository at this point in the history
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12302

git-svn-id: http://svn.whatwg.org/webapps@6103 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed May 6, 2011
1 parent 1adec1c commit 4e138f8
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 8 deletions.
9 changes: 5 additions & 4 deletions complete.html
Expand Up @@ -3375,6 +3375,7 @@ <h4 id=dependencies><span class=secno>2.2.2 </span>Dependencies</h4>
<ul class=brief><li><dfn id=event><code>Event</code></dfn> interface</li>
<li><dfn id=eventtarget><code>EventTarget</code></dfn> interface</li>
<li><dfn id=uievent><code>UIEvent</code></dfn> interface</li>
<li><dfn id=mouseevent><code>MouseEvent</code></dfn> interface</li>

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

Expand Down Expand Up @@ -52249,10 +52250,10 @@ <h5 id=context-menus><span class=secno>4.11.4.3 </span><dfn>Context menus</dfn><
<dl class=switch><dt>If the user requested a context menu using a pointing device</dt>

<dd><p>The user agent must dispatch an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
cancelable, and that uses the <code>MouseEvent</code> interface, at
cancelable, and that uses the <code><a href=#mouseevent>MouseEvent</a></code> interface, at
the element for which the menu was requested. The context
information of the event must be set to the same values as the last
<code>MouseEvent</code> user interaction event that was dispatched
<code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was dispatched
as part of the gesture that that was interpreted as a request for
the context menu.</dd>

Expand Down Expand Up @@ -67257,7 +67258,7 @@ <h5 id=event-firing><span class=secno>7.1.6.3 </span>Event firing</h5>
mouse event named <var title="">e</var></dfn> means that an event
with the name <var title="">e</var>, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code>MouseEvent</code>
otherwise stated), and which uses the <code><a href=#mouseevent>MouseEvent</a></code>
interface, must be dispatched at the given target. The event object
must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes
set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes set according to the current
Expand Down Expand Up @@ -71172,7 +71173,7 @@ <h4 id=the-dragevent-interface><span class=secno>8.7.4 </span>The <code><a href=
<p>The drag-and-drop processing model involves several events. They
all use the <code><a href=#dragevent>DragEvent</a></code> interface.</p>

<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : <span>MouseEvent</span> {
<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : <a href=#mouseevent>MouseEvent</a> {
readonly attribute <a href=#datatransfer>DataTransfer</a> <a href=#dom-dragevent-datatransfer title=dom-DragEvent-dataTransfer>dataTransfer</a>;

void <a href=#dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dummyArg<!-- used to be viewArg, back when we had views -->, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
Expand Down
9 changes: 5 additions & 4 deletions index
Expand Up @@ -3400,6 +3400,7 @@ explained in the previous section, which talks about RFC 2119. -->
<ul class=brief><li><dfn id=event><code>Event</code></dfn> interface</li>
<li><dfn id=eventtarget><code>EventTarget</code></dfn> interface</li>
<li><dfn id=uievent><code>UIEvent</code></dfn> interface</li>
<li><dfn id=mouseevent><code>MouseEvent</code></dfn> interface</li>

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

Expand Down Expand Up @@ -52277,10 +52278,10 @@ fur
<dl class=switch><dt>If the user requested a context menu using a pointing device</dt>

<dd><p>The user agent must dispatch an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
cancelable, and that uses the <code>MouseEvent</code> interface, at
cancelable, and that uses the <code><a href=#mouseevent>MouseEvent</a></code> interface, at
the element for which the menu was requested. The context
information of the event must be set to the same values as the last
<code>MouseEvent</code> user interaction event that was dispatched
<code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was dispatched
as part of the gesture that that was interpreted as a request for
the context menu.</dd>

Expand Down Expand Up @@ -67305,7 +67306,7 @@ interface <dfn id=function>Function</dfn> {
mouse event named <var title="">e</var></dfn> means that an event
with the name <var title="">e</var>, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code>MouseEvent</code>
otherwise stated), and which uses the <code><a href=#mouseevent>MouseEvent</a></code>
interface, must be dispatched at the given target. The event object
must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes
set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes set according to the current
Expand Down Expand Up @@ -71226,7 +71227,7 @@ interface <dfn>FunctionObjectCallback</dfn> {
<p>The drag-and-drop processing model involves several events. They
all use the <code><a href=#dragevent>DragEvent</a></code> interface.</p>

<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : <span>MouseEvent</span> {
<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : <a href=#mouseevent>MouseEvent</a> {
readonly attribute <a href=#datatransfer>DataTransfer</a> <a href=#dom-dragevent-datatransfer title=dom-DragEvent-dataTransfer>dataTransfer</a>;

void <a href=#dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dummyArg<!-- used to be viewArg, back when we had views -->, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
Expand Down
1 change: 1 addition & 0 deletions source
Expand Up @@ -2368,6 +2368,7 @@ explained in the previous section, which talks about RFC 2119. -->
<li><dfn><code>Event</code></dfn> interface</li>
<li><dfn><code>EventTarget</code></dfn> interface</li>
<li><dfn><code>UIEvent</code></dfn> interface</li>
<li><dfn><code>MouseEvent</code></dfn> interface</li>

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

Expand Down

0 comments on commit 4e138f8

Please sign in to comment.