--- a/source/xml-source.xml	Fri Feb 24 23:01:36 2006 +0900
+++ b/source/xml-source.xml	Fri Feb 24 23:30:37 2006 +0900
@@ -4599,14 +4599,14 @@
          <code>ev:mousedown</code>, <code>ev:mouseup</code>, and
          <code>ev:click</code>. The sequence of these events is:
          <code>ev:mousedown</code>, <code>ev:mouseup</code>, and
-         <code>ev:click</code>. Note that, given the definition of a
-         click, if one or more of the event types
+         <code>ev:click</code>. It depends on the environment
+         configuration whether the event type <code>ev:click</code> can
+         occur if one or more of the event types
          <code>ev:mouseover</code>, <code>ev:mousemove</code>, and
          <code>ev:mouseout</code> occur between the press and release of
-         the pointing device button, the event type
-         <code>ev:click</code> cannot occur. In the case of nested
-         elements, this event type is always targeted at the most deeply
-         nested element.
+         the pointing device button. In the case of nested elements,
+         this event type is always targeted at the most deeply nested
+         element.
         </p>
 
         <ednote>
@@ -4616,15 +4616,6 @@
           concerned with making <code>ev:click</code> more generic.
          </edtext>
         </ednote>
-
-        <ednote>
-         <edtext>
-          There is an open issue
-          <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/8'>ISSUE-8</loc>
-          concerned with whether <code>ev:click</code> can occur
-          contrary to what is defined above.
-         </edtext>
-        </ednote>
        </def>
       </gitem>
      </glist>