removed hasEventListenerNS and willTriggerNS as per 23 Feb 2006 f2f; updated some references (@@ need to check for more copy and paste errors in the references section...)
authorbjoern
Fri, 24 Feb 2006 03:19:24 +0900
changeset 1 71c058597322
parent 0 07d7e45424a6
child 2 c2950306b7e7
removed hasEventListenerNS and willTriggerNS as per 23 Feb 2006 f2f; updated some references (@@ need to check for more copy and paste errors in the references section...)
source/xml-source.xml
--- a/source/xml-source.xml	Wed Feb 22 21:53:46 2006 +0900
+++ b/source/xml-source.xml	Fri Feb 24 03:19:24 2006 +0900
@@ -2983,146 +2983,6 @@
 <!-- No exceptions -->
        </raises>
       </method>
-
-      <method name="willTriggerNS" since="DOM Level 3" id="Events3-willTriggerNS">
-       <descr>
-        <p>
-         This method allows the DOM application to know if an event
-         listener, attached to this <code>EventTarget</code> or one of
-         its ancestors, will be triggered by the specified event type
-         during the dispatch of the event to this event target or one of
-         its descendants as defined in
-         <specref ref="Events-listeners-activation"/>. If the intrinsic
-         bubbling behavior of the event type is not known to the
-         implementation, the event type is assumed to bubble.
-        </p>
-       </descr>
-
-       <parameters>
-        <param name="namespaceURI" type="DOMString" attr="in">
-         <descr>
-          <p>
-           Specifies the <code>Event.namespaceURI</code> associated with
-           the event.
-          </p>
-
-          <ednote>
-           <edtext>
-            There is an open issue
-            <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/4'>ISSUE-4</loc>
-            concerned with what should happen if this parameter is
-            <code>null</code> or the empty string.
-           </edtext>
-          </ednote>
-         </descr>
-        </param>
-
-        <param name="type" type="DOMString" attr="in">
-         <descr>
-          <p>
-           Specifies the <code>Event.type</code> associated with the
-           event.
-          </p>
-
-          <ednote>
-           <edtext>
-            There is an open issue
-            <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/4'>ISSUE-4</loc>
-            concerned with what should happen if this parameter is
-            <code>null</code> or the empty string.
-           </edtext>
-          </ednote>
-         </descr>
-        </param>
-       </parameters>
-
-       <returns type="boolean">
-        <descr>
-         <p>
-          <code>true</code> if an event listener will be triggered on
-          the <code>EventTarget</code> with the specified event type,
-          <code>false</code> otherwise.
-         </p>
-        </descr>
-       </returns>
-
-       <raises/>
-      </method>
-
-      <method name="hasEventListenerNS" since="DOM Level 3" id="Events3-hasEventListenerNS">
-       <descr>
-        <p>
-         This method allows the DOM application to know if this
-         <code>EventTarget</code> contains an event listener registered
-         for the specified event type. This is useful for determining at
-         which nodes within a hierarchy altered handling of specific
-         event types has been introduced, but should not be used to
-         determine whether the specified event type triggers an event
-         listener (see <code>EventTarget.willTriggerNS()</code>).
-        </p>
-
-        <ednote>
-         <edtext>
-          There is an open issue
-          <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/5'>ISSUE-5</loc>
-          concerned with whether this method considers only listeners
-          registered with DOM APIs, or whether listeners registered
-          using markup or similar means are considered aswell, and which
-          specification is responsible to define this.
-         </edtext>
-        </ednote>
-       </descr>
-
-       <parameters>
-        <param name="namespaceURI" type="DOMString" attr="in">
-         <descr>
-          <p>
-           Specifies the <code>Event.namespaceURI</code> associated with
-           the event.
-          </p>
-
-          <ednote>
-           <edtext>
-            There is an open issue
-            <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/4'>ISSUE-4</loc>
-            concerned with what should happen if this parameter is
-            <code>null</code> or the empty string.
-           </edtext>
-          </ednote>
-         </descr>
-        </param>
-
-        <param name="type" type="DOMString" attr="in">
-         <descr>
-          <p>
-           Specifies the <code>Event.type</code> associated with the
-           event.
-          </p>
-
-          <ednote>
-           <edtext>
-            There is an open issue
-            <loc href='http://www.w3.org/2005/06/tracker/webapi/issues/4'>ISSUE-4</loc>
-            concerned with what should happen if this parameter is
-            <code>null</code> or the empty string.
-           </edtext>
-          </ednote>
-         </descr>
-        </param>
-       </parameters>
-
-       <returns type="boolean">
-        <descr>
-         <p>
-          <code>true</code> if an event listener is registered on this
-          <code>EventTarget</code> for the specified event type,
-          <code>false</code> otherwise.
-         </p>
-        </descr>
-       </returns>
-
-       <raises/>
-      </method>
      </interface>
 <!-- Event listener interface -->
      <interface id="Events-EventListener" name="EventListener" since="DOM Level 2" role="ecmascript-function">
@@ -4096,7 +3956,6 @@
      </p>
 
      <definitions>
-<!-- $Date$ $Revision$ -->
 <!--[ TextEvent object description ]-->
       <interface name="TextEvent" inherits="UIEvent" id="Events-TextEvent" since="DOM Level 3">
        <descr>
@@ -5620,7 +5479,6 @@
      </p>
 
      <definitions>
-<!-- $Date$ $Revision$ -->
 <!--[ KeyboardEvent object description ]-->
       <interface name="KeyboardEvent" inherits="UIEvent" id="Events-KeyboardEvent" since="DOM Level 3">
        <descr>
@@ -13878,10 +13736,10 @@
      1.0</loc> is available at http://www.w3.org/TR/REC-xml.
     </bibl>
 
-    <bibl id="XML11" key="XML 1.1" href="http://www.w3.org/TR/2003/PR-xml11-20031105/">
+    <bibl id="XML11" key="XML 1.1" href="http://www.w3.org/TR/2004/REC-xml11-20040204/">
      <titleref>XML 1.1</titleref>, T. Bray, and al., Editors. World Wide
-     Web Consortium, November 2003. This version of the XML 1.1
-     Specification is http://www.w3.org/TR/2003/PR-xml11-20031105. The
+     Web Consortium, February 2004. This version of the XML 1.1
+     Specification is http://www.w3.org/TR/2004/REC-xml11-20040204. The
      <loc href="http://www.w3.org/TR/xml11/">latest version of XML
      1.1</loc> is available at http://www.w3.org/TR/xml11.
     </bibl>
@@ -13894,21 +13752,21 @@
      Base</loc> is available at http://www.w3.org/TR/xmlbase.
     </bibl>
 
-    <bibl id="InfoSet" key="XML Information Set" href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024/">
+    <bibl id="InfoSet" key="XML Information Set" href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">
      <titleref>XML Information Set</titleref>, J. Cowan and R. Tobin,
-     Editors. World Wide Web Consortium, 24 October 2001. This version
-     of the XML Information Set Recommendation is
-     http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The
+     Editors. World Wide Web Consortium, February 2004. This version of
+     the XML Information Set Recommendation is
+     http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The
      <loc href="http://www.w3.org/TR/xml-infoset/">latest version of XML
      Information Set</loc> is available at
      http://www.w3.org/TR/xml-infoset.
     </bibl>
 
-    <bibl id="XMLEvents" key="XML Events" href="http://www.w3.org/TR/2003/PR-xml-events-20030804/">
+    <bibl id="XMLEvents" key="XML Events" href="http://www.w3.org/TR/2003/REC-xml-events-20031014">
      <titleref>XML Events</titleref>, S. McCarron, S. Pemberton, and
-     T.V. Raman, Editors. World Wide Web Consortium, August 2003. This
+     T.V. Raman, Editors. World Wide Web Consortium, October 2003. This
      version of the XML Events specification is
-     http://www.w3.org/TR/2003/PR-xml-events-20030804. The
+     http://www.w3.org/TR/2003/REC-xml-events-20031014. The
      <loc href="http://www.w3.org/TR/xml-events/">latest version of XML
      Events</loc> is available at http://www.w3.org/TR/xml-events.
     </bibl>
@@ -13916,21 +13774,21 @@
     <bibl id="Namespaces" key="XML Namespaces" href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">
      <titleref>Namespaces in XML</titleref>, T. Bray, D. Hollander, and
      A. Layman, Editors. World Wide Web Consortium, 14 January 1999.
-     This version of the XML Information Set Recommendation is
+     This version of the Namespaces in XML Recommendation is
      http://www.w3.org/TR/1999/REC-xml-names-19990114. The
      <loc href="http://www.w3.org/TR/REC-xml-names/">latest version of
      Namespaces in XML</loc> is available at
      http://www.w3.org/TR/REC-xml-names.
     </bibl>
 
-    <bibl id="Namespaces11" key="XML Namespaces 1.1" href="http://www.w3.org/TR/2003/PR-xml-names11-20031105/">
+    <bibl id="Namespaces11" key="XML Namespaces 1.1" href="http://www.w3.org/TR/2004/REC-xml-names11-20040204/">
      <titleref>Namespaces in XML 1.1</titleref>, T. Bray, D. Hollander,
      A. Layman, and R. Tobin, Editors. World Wide Web Consortium,
-     November 2003. This version of the XML Information Set
+     February 2004. This version of the Namespaces in XML 1.1
      Specification is
-     http://www.w3.org/TR/2003/PR-xml-names11-20031105/. The
+     http://www.w3.org/TR/2004/REC-xml-names11-20040204/. The
      <loc href="http://www.w3.org/TR/xml-names11/">latest version of
-     Namespaces in XML</loc> is available at
+     Namespaces in XML 1.1</loc> is available at
      http://www.w3.org/TR/xml-names11/.
     </bibl>