W3C home > Mailing lists > Public > public-html-commits@w3.org > October 2009

html5/spec Overview.html,1.3496,1.3497

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 27 Oct 2009 19:47:05 +0000
To: public-html-commits@w3.org
Message-Id: <E1N2s0X-0005tQ-GA@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv22638

Modified Files:
	Overview.html 
Log Message:
remove more namespace mentions relating to event (whatwg r4364)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3496
retrieving revision 1.3497
diff -u -d -r1.3496 -r1.3497
--- Overview.html	27 Oct 2009 19:44:20 -0000	1.3496
+++ Overview.html	27 Oct 2009 19:47:01 -0000	1.3497
@@ -43576,34 +43576,35 @@
   firing a <code title="event-click">click</code> event on the
   element. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
 
-  <p><dfn id="fire-a-click-event" title="fire a click event">Firing a <code title="event-click">click</code> event</dfn> means that a <code title="event-click">click</code> event with no namespace, which
-  bubbles and is cancelable, and which uses the
-  <code>MouseEvent</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
+  <p><dfn id="fire-a-click-event" title="fire a click event">Firing a <code title="event-click">click</code> event</dfn> means that a <code title="event-click">click</code> event, which bubbles and is
+  cancelable, and which uses the <code>MouseEvent</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 state of the key input device, if any
   (false for any keys that are not available), its <code title="">detail</code> attribute set to 1, and its <code title="">relatedTarget</code> attribute set to null. The <code title="">getModifierState()</code> method on the object must return
   values appropriately describing the state of the key input device at
   the time the event is created.</p>
 
-  <p><dfn id="fire-a-simple-event" title="fire a simple event">Firing a simple event named
-  <var title="">e</var></dfn> means that an event with the name <var title="">e</var>, with no namespace, which does not bubble (except
-  where otherwise stated) and is not cancelable (except where
-  otherwise stated), and which uses the <code>Event</code> interface,
-  must be dispatched at the given target.</p>
+  <p><dfn id="fire-a-simple-event" title="fire a simple event">Firing a simple 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>Event</code> interface, must be dispatched at
+  the given target.</p>
 
 <!--
   <p><dfn title="fire a progress event">Firing a progress event named
   <var title="">e</var></dfn>, optionally in the context of a
   particular instance of the <span title="fetch">fetching
   algorithm</span>, means that an event with the name <var
-  title="">e</var>, with no namespace, which does not bubble (except
-  where otherwise stated) and is not cancelable (except where
-  otherwise stated), and which uses the <code>ProgressEvent</code>
-  interface, must be dispatched at the given target element. If there
-  is a <span title="fetch">fetching algorithm</span>, and the
-  <span>URL</span> being <span title="fetch">fetched</span> has the
-  <span>same origin</span> as the <code>Document</code> of the target
-  element, then the <code
+  title="">e</var>, which does not bubble (except where otherwise
+  stated) and is not cancelable (except where otherwise stated), and
+  which uses the <code>ProgressEvent</code> interface, must be
+  dispatched at the given target element. If there is a <span
+  title="fetch">fetching algorithm</span>, and the <span>URL</span>
+  being <span title="fetch">fetched</span> has the <span>same
+  origin</span> as the <code>Document</code> of the target element,
+  then the <code
   title="dom-ProgressEvents-lengthComputable">lengthComputable</code>
   attribute must be set to true if the <span title="fetch">fetching
   algorithm</span>'s subject has a known <span
@@ -45905,9 +45906,9 @@
      <li><p>For each <a href="#cache-host">cache host</a> associated with an
      <a href="#application-cache">application cache</a> in <var title="">cache
      group</var>, <a href="#queue-a-task">queue a task</a> to fire an event with the
-     name <code title="event-appcache-progress"><a href="#event-appcache-progress">progress</a></code>, with
-     no namespace, which does not bubble, which is cancelable, and
-     which uses the <code>ProgressEvent</code> interface, at the
+     name <code title="event-appcache-progress"><a href="#event-appcache-progress">progress</a></code>, which
+     does not bubble, which is cancelable, and which uses the
+     <code>ProgressEvent</code> interface, at the
      <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
      host</a>. The <code title="dom-ProgressEvents-lengthComputable">lengthComputable</code>
      attribute must be set to true, the <code title="dom-ProgressEvents-total">total</code> attribute must be
@@ -46032,8 +46033,8 @@
 
    <li><p>For each <a href="#cache-host">cache host</a> associated with an
    <a href="#application-cache">application cache</a> in <var title="">cache group</var>,
-   <a href="#queue-a-task">queue a task</a> to fire an event with the name <code title="event-appcache-progress"><a href="#event-appcache-progress">progress</a></code>, with no namespace,
-   which does not bubble, which is cancelable, and which uses the
+   <a href="#queue-a-task">queue a task</a> to fire an event with the name <code title="event-appcache-progress"><a href="#event-appcache-progress">progress</a></code>, which does not
+   bubble, which is cancelable, and which uses the
    <code>ProgressEvent</code> interface, at the
    <code><a href="#applicationcache">ApplicationCache</a></code> singleton of the <a href="#cache-host">cache
    host</a>. The <code title="dom-ProgressEvents-lengthComputable">lengthComputable</code>
@@ -47046,10 +47047,9 @@
     <dl class="switch"><dt>If the <a href="#current-document-readiness">current document readiness</a> is set to the
      string "complete"</dt>
 
-     <dd><p>Synchronously fire a <dfn id="event-popstate" title="event-popstate"><code>popstate</code></dfn> event in no
-     namespace on the <code><a href="#window">Window</a></code> object of the
-     <code>Document</code>, using the <code><a href="#popstateevent">PopStateEvent</a></code>
-     interface, with the <code title="dom-PopStateEvent-state"><a href="#dom-popstateevent-state">state</a></code> attribute set to the
+     <dd><p>Synchronously fire a <dfn id="event-popstate" title="event-popstate"><code>popstate</code></dfn> event on the
+     <code><a href="#window">Window</a></code> object of the <code>Document</code>, using
+     the <code><a href="#popstateevent">PopStateEvent</a></code> interface, with the <code title="dom-PopStateEvent-state"><a href="#dom-popstateevent-state">state</a></code> attribute set to the
      value of <var title="">state</var>. This event must bubble but
      not be cancelable and has no default action.</dd>
 
@@ -48192,8 +48192,8 @@
   it must run the following steps.</p>
 
   <ol><li><p>Let <var title="">event</var> be a new
-   <code><a href="#beforeunloadevent">BeforeUnloadEvent</a></code> event object with the name <code title="event-beforeunload">beforeunload</code>, with no namespace,
-   which does not bubble but is cancelable.</li>
+   <code><a href="#beforeunloadevent">BeforeUnloadEvent</a></code> event object with the name <code title="event-beforeunload">beforeunload</code>, which does not
+   bubble but is cancelable.</li>
 
    <li><p>Dispatch <var title="">event</var> at the
    <code>Document</code>'s <code><a href="#window">Window</a></code> object.</li>
@@ -61120,7 +61120,7 @@
    <code>Document</code>'s <code><a href="#window">Window</a></code> object.</li>
 
    <li><p>If the <code>Document</code> has a <a href="#pending-state-object">pending state
-   object</a>, then <a href="#queue-a-task">queue a task</a> to fire a <code title="event-popstate"><a href="#event-popstate">popstate</a></code> event in no namespace on the
+   object</a>, then <a href="#queue-a-task">queue a task</a> to fire a <code title="event-popstate"><a href="#event-popstate">popstate</a></code> event at the
    <code>Document</code>'s <code><a href="#window">Window</a></code> object using the
    <code><a href="#popstateevent">PopStateEvent</a></code> interface, with the <code title="dom-PopStateEvent-state"><a href="#dom-popstateevent-state">state</a></code> attribute set to the
    current value of the <a href="#pending-state-object">pending state object</a>. This event
Received on Tuesday, 27 October 2009 20:21:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 20:21:40 GMT