[html5] r4364 - [e] (0) remove more namespace mentions relating to event Fixing http://www.w3.or [...]
whatwg at whatwg.org
whatwg at whatwg.org
Tue Oct 27 12:47:02 PDT 2009
Author: ianh
Date: 2009-10-27 12:46:58 -0700 (Tue, 27 Oct 2009)
New Revision: 4364
Modified:
complete.html
index
source
Log:
[e] (0) remove more namespace mentions relating to event
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8080
Modified: complete.html
===================================================================
--- complete.html 2009-10-27 19:44:17 UTC (rev 4363)
+++ complete.html 2009-10-27 19:46:58 UTC (rev 4364)
@@ -51497,34 +51497,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
@@ -54016,9 +54017,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
@@ -54143,8 +54144,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>
@@ -55238,10 +55239,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>
@@ -56422,8 +56422,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>
@@ -58208,11 +58208,11 @@
storage</a>).</p>
<p>When this happens, the user agent must <a href=#queue-a-task>queue a task</a>
- to fire an event with the name <code><a href=#storage-0>storage</a></code>, with no
- namespace, which does not bubble and is not cancelable, and which
- uses the <code><a href=#storageevent>StorageEvent</a></code> interface, at each
- <code><a href=#window>Window</a></code> object whose <code>Document</code> object has a
- <code><a href=#storage-0>Storage</a></code> object that is affected.</p>
+ to fire an event with the name <code><a href=#storage-0>storage</a></code>, which does not
+ bubble and is not cancelable, and which uses the
+ <code><a href=#storageevent>StorageEvent</a></code> interface, at each <code><a href=#window>Window</a></code>
+ object whose <code>Document</code> object has a <code><a href=#storage-0>Storage</a></code>
+ object that is affected.</p>
<p class=note>This includes <code>Document</code> objects that are
not <a href=#fully-active>fully active</a>, but events fired on those are ignored
@@ -76515,7 +76515,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
Modified: index
===================================================================
--- index 2009-10-27 19:44:17 UTC (rev 4363)
+++ index 2009-10-27 19:46:58 UTC (rev 4364)
@@ -48639,34 +48639,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
@@ -51158,9 +51159,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
@@ -51285,8 +51286,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>
@@ -52380,10 +52381,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>
@@ -53564,8 +53564,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>
@@ -67486,7 +67486,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
Modified: source
===================================================================
--- source 2009-10-27 19:44:17 UTC (rev 4363)
+++ source 2009-10-27 19:46:58 UTC (rev 4364)
@@ -57974,13 +57974,12 @@
<p><dfn 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="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
@@ -57991,26 +57990,26 @@
values appropriately describing the state of the key input device at
the time the event is created.</p>
- <p><dfn 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 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
@@ -60889,9 +60888,9 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to fire an event with the
- name <code title="event-appcache-progress">progress</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">progress</code>, which
+ does not bubble, which is cancelable, and which uses the
+ <code>ProgressEvent</code> interface, at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The <code
title="dom-ProgressEvents-lengthComputable">lengthComputable</code>
@@ -61031,8 +61030,8 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache group</var>,
<span>queue a task</span> to fire an event with the name <code
- title="event-appcache-progress">progress</code>, with no namespace,
- which does not bubble, which is cancelable, and which uses the
+ title="event-appcache-progress">progress</code>, which does not
+ bubble, which is cancelable, and which uses the
<code>ProgressEvent</code> interface, at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The <code
@@ -62318,10 +62317,9 @@
string "complete"</dt>
<dd><p>Synchronously fire a <dfn
- title="event-popstate"><code>popstate</code></dfn> event in no
- namespace on the <code>Window</code> object of the
- <code>Document</code>, using the <code>PopStateEvent</code>
- interface, with the <code
+ title="event-popstate"><code>popstate</code></dfn> event on the
+ <code>Window</code> object of the <code>Document</code>, using
+ the <code>PopStateEvent</code> interface, with the <code
title="dom-PopStateEvent-state">state</code> attribute set to the
value of <var title="">state</var>. This event must bubble but
not be cancelable and has no default action.</p></dd>
@@ -63689,8 +63687,8 @@
<li><p>Let <var title="">event</var> be a new
<code>BeforeUnloadEvent</code> event object with the name <code
- title="event-beforeunload">beforeunload</code>, with no namespace,
- which does not bubble but is cancelable.</p></li>
+ title="event-beforeunload">beforeunload</code>, which does not
+ bubble but is cancelable.</p></li>
<li><p>Dispatch <var title="">event</var> at the
<code>Document</code>'s <code>Window</code> object.</p></li>
@@ -65733,11 +65731,11 @@
storage</a>).</p>
<p>When this happens, the user agent must <span>queue a task</span>
- to fire an event with the name <code>storage</code>, with no
- namespace, which does not bubble and is not cancelable, and which
- uses the <code>StorageEvent</code> interface, at each
- <code>Window</code> object whose <code>Document</code> object has a
- <code>Storage</code> object that is affected.</p>
+ to fire an event with the name <code>storage</code>, which does not
+ bubble and is not cancelable, and which uses the
+ <code>StorageEvent</code> interface, at each <code>Window</code>
+ object whose <code>Document</code> object has a <code>Storage</code>
+ object that is affected.</p>
<p class="note">This includes <code>Document</code> objects that are
not <span>fully active</span>, but events fired on those are ignored
@@ -86124,7 +86122,7 @@
<li><p>If the <code>Document</code> has a <span>pending state
object</span>, then <span>queue a task</span> to fire a <code
- title="event-popstate">popstate</code> event in no namespace on the
+ title="event-popstate">popstate</code> event at the
<code>Document</code>'s <code>Window</code> object using the
<code>PopStateEvent</code> interface, with the <code
title="dom-PopStateEvent-state">state</code> attribute set to the
More information about the Commit-Watchers
mailing list