Skip to content

Commit

Permalink
[e] (0) remove obsolete notes and issues; change remaining occurances…
Browse files Browse the repository at this point in the history 
… of xml-events namespace to no namespace

git-svn-id: http://svn.whatwg.org/webapps@540 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Feb 2, 2007
1 parent 4ee3fcf commit 122c778
Show file tree
Hide file tree
Showing 2 changed files with 56 additions and 86 deletions.
63 changes: 24 additions & 39 deletions index
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5538,9 +5538,7 @@ data:text/xml,<script xmlns="http://www.w3.org/1999/xhtml"><![CDATA[ alert('test
pointing device, the default action of the event that triggers the
activation must, instead of being activating the element directly, be to
<a href="#firing">fire a <code title="">click</code> event</a> on the same
element.</p>
<!-- XXX this part is wrong; we should define it in terms of ANY
click event, possibly requiring trusted clicks: -->
element.

<p>The default action of this <code title=event-click>click</code> event,
or of the real <code title=event-click>click</code> event if the element
Expand All @@ -5558,15 +5556,8 @@ data:text/xml,<script xmlns="http://www.w3.org/1999/xhtml"><![CDATA[ alert('test
<!-- XXX WF2: when this is merged into
this spec, update xrefs -->

<p class=note>Most interactive elements have content models that disallowed
nesting interactive elements.

<p class=big-issue> Need to define how default actions actually work. For
instance, if you click an event inside a link, the event is triggered on
that element, but then we'd like a click is sent on the link itself. So
how does that happen? Does the link have a bubbling listener that triggers
that second click event? what if there are multiple nested links, which
one should we send that event to?</p>
<p class=note>Most interactive elements have content models that disallow
nesting interactive elements.</p>
<!--
<li><span>Form control elements</span></li> XXX
-->
Expand Down Expand Up @@ -21747,9 +21738,8 @@ mpt says:

<p>When a state object in the session history is activated (which happens
in the cases described above), the user agent must fire a <dfn id=popstate
title=event-popstate><code>popstate</code></dfn> event in the
<code>http://www.w3.org/2001/xml-events</code> namespace on the <a
href="#the-body0">the body element</a> using the <code><a
title=event-popstate><code>popstate</code></dfn> event in no namespace on
the <a href="#the-body0">the body element</a> using the <code><a
href="#popstateevent">PopStateEvent</a></code> interface, with the state
object in the <code title=dom-PopStateEvent-state><a
href="#state0">state</a></code> attribute. This event bubbles but is not
Expand Down Expand Up @@ -21971,11 +21961,11 @@ user reload must be equivalent to .reload()
<code><a href="#windowhtml">WindowHTML</a></code> changes from false to
true.

<p>These events are in the <code>http://www.w3.org/2001/xml-events</code>
namespace, do bubble, are not cancelable, have no default action, and use
the normal <code>Event</code> interface. They must be fired on <a
href="#the-body0">the body element</a>. (As the events bubble, they will
reach the <code><a href="#windowhtml">WindowHTML</a></code> object.)</p>
<p>These events are in no namespace, do bubble, are not cancelable, have no
default action, and use the normal <code>Event</code> interface. They must
be fired on <a href="#the-body0">the body element</a>. (As the events
bubble, they will reach the <code><a
href="#windowhtml">WindowHTML</a></code> object.)</p>
<!-- XXX ononline onoffline need to be defined -->

<h4 id=custom-handlers><span class=secno>5.3.2. </span>Custom protocol and
Expand Down Expand Up @@ -22841,10 +22831,10 @@ interface <dfn id=storageitem>StorageItem</dfn> {
href="#globalStorageEvent">for global storage</a>).

<p>When this happens, a <code><a href="#storage2">storage</a></code> event
in the <code>http://www.w3.org/2001/xml-events</code> namespace, which
bubbles, is not cancelable, has no default action, and which uses the
<code><a href="#storageevent">StorageEvent</a></code> interface described
below, must be fired on <a href="#the-body0">the body element</a>.
in no namespace, which bubbles, is not cancelable, has no default action,
and which uses the <code><a href="#storageevent">StorageEvent</a></code>
interface described below, must be fired on <a href="#the-body0">the body
element</a>.

<p>However, it is possible (indeed, for session storage areas, likely) that
the target <code><a href="#htmldocument">HTMLDocument</a></code> object is
Expand Down Expand Up @@ -25786,9 +25776,8 @@ Test: Line 2</pre>

<li>
<p><code title="">Namespace</code> is the DOM3 namespace for the event.
For normal DOM events this would be <code
title="">http://www.w3.org/2001/xml-events</code>. If it isn't specified
the event namespace is null.
(For normal DOM events this would be null.) If it isn't specified the
event namespace is null.

<li>
<p><code title="">Class</code> is the interface used for the event, for
Expand All @@ -25806,9 +25795,8 @@ Test: Line 2</pre>

<ul>
<li>
<p>If <code title="">Namespace</code> is <code
title="">http://www.w3.org/2001/xml-events</code> or null and the
<code title="">Event</code> field exactly matches one of the events
<p>If <code title="">Namespace</code> is null and the <code
title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete">section
1.4.2 "Complete list of event types"</a>, then the Class defaults to
Expand Down Expand Up @@ -25851,9 +25839,8 @@ Test: Line 2</pre>

<ul>
<li>
<p>If <code title="">Namespace</code> is <code
title="">http://www.w3.org/2001/xml-events</code> or null and the
<code title="">Event</code> field exactly matches one of the events
<p>If <code title="">Namespace</code> is null and the <code
title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete">section
1.4.2 "Complete list of event types"</a>, then whether the event
Expand Down Expand Up @@ -25886,9 +25873,8 @@ Test: Line 2</pre>

<ul>
<li>
<p>If <code title="">Namespace</code> is <code
title="">http://www.w3.org/2001/xml-events</code> or null and the
<code title="">Event</code> field exactly matches one of the events
<p>If <code title="">Namespace</code> is null and the <code
title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete">section
1.4.2 "Complete list of event types"</a>, then whether the event is
Expand Down Expand Up @@ -26210,9 +26196,8 @@ document.getElementById('stock').addEventListener('stock change',

<h4 id=connection><span class=secno>7.2.3. </span>Connection Events</h4>

<p>All the events described in this section are events in the
<code>http://www.w3.org/2001/xml-events</code> namespace, which do not
bubble, are not cancelable, and have no default action.
<p>All the events described in this section are events in no namespace,
which do not bubble, are not cancelable, and have no default action.

<p>The <dfn id=open2 title=event-connection-open><code>open</code></dfn>
event is fired when the connection is established. UAs must use the normal
Expand Down
79 changes: 32 additions & 47 deletions source
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4372,8 +4372,6 @@ data:text/xml,<script xmlns="http://www.w3.org/1999/xhtml"><![CDATA[ alert('test
directly, be to <span>fire a <code title="">click</code> event</span>
on the same element.</p>

<!-- XXX this part is wrong; we should define it in terms of ANY
click event, possibly requiring trusted clicks: -->
<p>The default action of this <code title="event-click">click</code>
event, or of the real <code title="event-click">click</code> event
if the element was activated by clicking a pointing device, must be
Expand All @@ -4391,15 +4389,7 @@ data:text/xml,<script xmlns="http://www.w3.org/1999/xhtml"><![CDATA[ alert('test
this spec, update xrefs -->

<p class="note">Most interactive elements have content models that
disallowed nesting interactive elements.</p>

<p class="big-issue"> Need to define how default actions actually
work. For instance, if you click an event inside a link, the event
is triggered on that element, but then we'd like a click is sent on
the link itself. So how does that happen? Does the link have a
bubbling listener that triggers that second click event? what if
there are multiple nested links, which one should we send that event
to?</p>
disallow nesting interactive elements.</p>

<!--
<li><span>Form control elements</span></li> XXX
Expand Down Expand Up @@ -19582,9 +19572,8 @@ mpt says:

<p>When a state object in the session history is activated (which
happens in the cases described above), the user agent must fire a
<dfn title="event-popstate"><code>popstate</code></dfn> event in the
<code>http://www.w3.org/2001/xml-events</code> namespace on the
<span>the body element</span> using the
<dfn title="event-popstate"><code>popstate</code></dfn> event in no
namespace on the <span>the body element</span> using the
<code>PopStateEvent</code> interface, with the state object in the
<code title="dom-PopStateEvent-state">state</code> attribute. This
event bubbles but is not cancelable and has no default action.</p>
Expand Down Expand Up @@ -19798,12 +19787,11 @@ user reload must be equivalent to .reload()
title="dom-navigator-onLine">navigator.onLine</code> attribute of
the <code>WindowHTML</code> changes from false to true.</p>

<p>These events are in the
<code>http://www.w3.org/2001/xml-events</code> namespace, do bubble,
are not cancelable, have no default action, and use the normal
<code>Event</code> interface. They must be fired on <span>the body
element</span>. (As the events bubble, they will reach the
<code>WindowHTML</code> object.)</p>
<p>These events are in no namespace, do bubble, are not cancelable,
have no default action, and use the normal <code>Event</code>
interface. They must be fired on <span>the body element</span>. (As
the events bubble, they will reach the <code>WindowHTML</code>
object.)</p>

<!-- XXX ononline onoffline need to be defined -->

Expand Down Expand Up @@ -20686,11 +20674,10 @@ interface <dfn>StorageItem</dfn> {
href="#sessionStorageEvent">for session storage</a>, <a
href="#globalStorageEvent">for global storage</a>).</p>

<p>When this happens, a <code>storage</code> event in the
<code>http://www.w3.org/2001/xml-events</code> namespace, which
bubbles, is not cancelable, has no default action, and which uses
the <code>StorageEvent</code> interface described below, must be
fired on <span>the body element</span>.</p>
<p>When this happens, a <code>storage</code> event in no namespace,
which bubbles, is not cancelable, has no default action, and which
uses the <code>StorageEvent</code> interface described below, must
be fired on <span>the body element</span>.</p>

<p>However, it is possible (indeed, for session storage areas,
likely) that the target <code>HTMLDocument</code> object is not
Expand Down Expand Up @@ -23611,9 +23598,8 @@ Test: Line 2</pre>
then no event will be synthesised, and the other data will be
ignored.</p></li>

<li><p><code title="">Namespace</code> is the DOM3 namespace for the event.
For normal DOM events this would be
<code title="">http://www.w3.org/2001/xml-events</code>. If it isn't
<li><p><code title="">Namespace</code> is the DOM3 namespace for
the event. (For normal DOM events this would be null.) If it isn't
specified the event namespace is null.</p></li>

<li><p><code title="">Class</code> is the interface used for the event, for
Expand All @@ -23629,8 +23615,7 @@ Test: Line 2</pre>
specified it is defaulted based on the event name as follows:</p>

<ul>
<li><p>If <code title="">Namespace</code> is
<code title="">http://www.w3.org/2001/xml-events</code> or null and the
<li><p>If <code title="">Namespace</code> is null and the
<code title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete">section
Expand Down Expand Up @@ -23668,13 +23653,13 @@ Test: Line 2</pre>
defaulted based on the event name as follows:</p>

<ul>
<li><p>If <code title="">Namespace</code> is <code title="">http://www.w3.org/2001/xml-events</code>
or null and the <code title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete"
>section 1.4.2 "Complete list of event types"</a>, then whether
the event bubbles depends on whether the DOM3 Events spec specifies
that that event should bubble or not. <a
<li><p>If <code title="">Namespace</code> is null and the <code
title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete">section
1.4.2 "Complete list of event types"</a>, then whether the event
bubbles depends on whether the DOM3 Events spec specifies that
that event should bubble or not. <a
href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>

<div class="example">
Expand All @@ -23698,13 +23683,13 @@ Test: Line 2</pre>
defaulted based on the event name as follows:</p>

<ul>
<li><p>If <code title="">Namespace</code> is <code title="">http://www.w3.org/2001/xml-events</code>
or null and the <code title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete"
>section 1.4.2 "Complete list of event types"</a>, then whether
the event is cancelable depends on whether the DOM3 Events spec
specifies that that event should be cancelable or not. <a
<li><p>If <code title="">Namespace</code> is null and the <code
title="">Event</code> field exactly matches one of the events
specified by DOM3 Events in <a
href="http://www.w3.org/TR/DOM-Level-3-Events/events.html#Events-EventTypes-complete">section
1.4.2 "Complete list of event types"</a>, then whether the event
is cancelable depends on whether the DOM3 Events spec specifies
that that event should be cancelable or not. <a
href="#refsDOM3EVENTS">[DOM3EVENTS]</a></p>

<div class="example">
Expand Down Expand Up @@ -24007,9 +23992,9 @@ document.getElementById('stock').addEventListener('stock change',

<h4>Connection Events</h4>

<p>All the events described in this section are events in the
<code>http://www.w3.org/2001/xml-events</code> namespace, which do
not bubble, are not cancelable, and have no default action.</p>
<p>All the events described in this section are events in no
namespace, which do not bubble, are not cancelable, and have no
default action.</p>

<p>The <dfn title="event-connection-open"><code>open</code></dfn>
event is fired when the connection is established. UAs must use the
Expand Down

0 comments on commit 122c778

Please sign in to comment.