svg2: remove reference to UI Events and switch to DOM3, fix event han...

details:   https://svgwg.org/hg/svg2/rev/d5404f7c7a6f
branches:  
changeset: 577:d5404f7c7a6f
user:      Richard Schwerdtfeger <schwer@us.ibm.com>
date:      Tue Dec 17 16:24:20 2013 -0600
description:
remove reference to UI Events and switch to DOM3, fix event handler reference

diffstat:

 master/interact.html |  13 +++++--------
 master/struct.html   |   2 +-
 master/svgdom.html   |   6 +++---
 3 files changed, 9 insertions(+), 12 deletions(-)

diffs (169 lines):

diff --git a/master/interact.html b/master/interact.html
--- a/master/interact.html
+++ b/master/interact.html
@@ -58,17 +58,17 @@ the SVG language:</p>
 <p>Related information can be found in other chapters:</p>
 
 <ul>
   <li>hyperlinks are discussed in <a href="linking.html">Links</a></li>
 
   <li>scripting and event attributes are discussed in <a href="script.html">Scripting</a></li>
 
   <li>SVG's relationship to DOM3 events is discussed in
-  <a href="svgdom.html#RelationshipWithDOM3andUIEvents">Relationship with DOM3 and UI Events</a></li>
+  <a href="svgdom.html#RelationshipWithDOM3Events">Relationship with DOM3 Events</a></li>
 
   <li>animation is discussed in <a href="animate.html">Animation</a></li>
 </ul>
 
 <h2 id="SVGEvents">Complete list of supported events</h2>
 
 <div class="annotation svg2-requirement">
   <table>
@@ -169,17 +169,17 @@ the SVG language:</p>
   <li>SVG's <a>animation elements</a> can be defined to begin or end based on
   events.</li>
 </ul>
 
 <p>The following table lists all of the events which are
 recognized and supported in SVG. The <em>Event name</em> in the
 first column is the name to use within SVG's <a>animation elements</a> to
 define the events which can start or end animations. The
-<em>DOM3 or UI Event name</em> in the second column is the name to use when
+<em>DOM3 Event name</em> in the second column is the name to use when
 defining <a href="http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/#widl-EventTarget-addEventListener">DOM 3 event listeners</a>
 ([<a href="refs.html#ref-DOM3EVENTS">DOM3EVENTS</a>], section 4.3).
 The <em>Event attribute name</em> in the fourth column contains the
 corresponding name of the <a href="script.html#EventAttributes">event attributes</a>
 that can be attached to elements in the SVG language.</p>
 
 <p>Requirements in the table on whether an event of a given type
 bubbles or is cancelable apply only to events that are created and
@@ -188,23 +188,20 @@ using the <code>createEvent</code> metho
 or be cancelable with the
 <a class='idlattr' href='http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/#widl-Event-initEvent'>initEvent</a>
 method.</p>
 
 <p class="issue">Having all these SVG-specific duplicates of standard DOM events isn't
 ideal.  How much can we remove?  SVGLoad in particular, and how it is currently
 required to fire for every element.</p>
 
-<p class="issue">DOM 3 and UI Event both define a keyboard event where UI Event introduced a key code which appears to be necessary per the WebApps effort. UI Event is an extension to KeyboardEvent in DOM 3. The group needs to discuss whether to use the UIEvent or DOM3 Event for keyboard. Also, HTML has taken on DOM 4 events and the group needes to decide what to do with this long term. Additionally, DOMActivate does not appear in the UI Events or DOM 3 Events Specs. Regarding the activate event, user agents treat click the same as activate. 
-</p>
-
     <table  class="vert event-table">
       <tr>
         <th>Event name and description</th>
-        <th>DOM3 or UI Event name</th>
+        <th>DOM3 Event name</th>
         <th>Event category</th>
         <th>Event attribute name</th>
       </tr>
       <tr>
         <td id="FocusEvent"><p class="event-name"><strong>focus</strong></p>
           <p>Occurs when an element receives focus. The focus must be given to the element before the dispatch of this event type.</p></td>
         <td>(same)</td>
         <td><a
@@ -244,30 +241,30 @@ required to fire for every element.</p>
       </tr>
 
       <tr>
         <td id="KeyDownEvent"><p class="event-name"><strong>keydown</strong></p>
         <p>Occurs when a key is pressed down. The keydown event type is device dependent and relies on the capabilities         of the input devices and how they are mapped in the operating system.
         </p></td>
         <td>(same)</td>
         <td><a
-        href="http://www.w3.org/TR/uievents/#keyboard-event-interface">
+        href="http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/#interface-KeyboardEvent">
         KeyboardEvent</a></td>
         <td><a
         href="script.html#OnKeyDownEventAttribute">onkeydown</a></td>
       </tr>
       <tr>
         <td id="KeyUpEvent"><p class="event-name"><strong>keyup</strong></p>
         <p>A user agent must dispatch this event when a key is released. The keyup event 
         type is device dependent and relies on the capabilities of the input devices and 
         how they are mapped in the operating system.
         </p></td>
         <td>(same)</td>
         <td><a
-        href="http://www.w3.org/TR/uievents/#keyboard-event-interface">
+        href="http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/#interface-KeyboardEvent">
         KeyboardEvent</a></td>
         <td><a
         href="script.html#OnKeyUpEventAttribute">onkeyup</a></td>
       </tr>
       <tr>
         <td id="ClickEvent"><p class="event-name"><strong>click</strong></p>
         <p>Occurs when the pointing device button is clicked over
         an element or when the pointer is otherwise activated in a manner that simulates such an action. A click is defined as a mousedown and mouseup
diff --git a/master/struct.html b/master/struct.html
--- a/master/struct.html
+++ b/master/struct.html
@@ -537,17 +537,17 @@ create SVG fragments.</p>
 <p>If an SVG document is likely to be referenced as a component
 of another document, the author will often want to include a
 <a>'viewBox'</a> attribute on the <a>outermost svg element</a> of the
 referenced document. This attribute provides a convenient way to design
 SVG documents to scale-to-fit into an arbitrary viewport.</p>
 
 <p id="SVGElementEventHandlerAttributes">The <a>'svg'</a> element exposes as <a>event handler content attributes</a> a number of the <a>event handlers</a> of the <a>Window</a> object. It also mirrors their <a>event handler IDL attributes</a>.</p>
 
-<p>The <a>onblur</a>, <a>onerror</a>, <a>onfocus</a>, <a>onload</a>, and <a>onscroll</a> <a>event handlers</a> of the <a>Window</a> object, exposed on the <a>'svg'</a> element,
+<p>The <a href="script.html#OnBlurEventAttribute">onblur</a>, <a>onerror</a>, <a href="script.html#OnFocusEventAttribute">onfocus</a>, <a>onload</a>, and <a>onscroll</a> <a>event handlers</a> of the <a>Window</a> object, exposed on the <a>'svg'</a> element,
 replace the generic <a>event handlers</a> with the same names normally supported by <a>SVG elements</a>.</p>
 
 <p class="issue">The above paragraphs feel out of place just after the list
 of attributes specific to <a>'svg'</a>.</p>
 
 </edit:with>
 
 <h2 id="Groups">Grouping: the <span class='element-name'>'g'</span> element</h2>
diff --git a/master/svgdom.html b/master/svgdom.html
--- a/master/svgdom.html
+++ b/master/svgdom.html
@@ -80,23 +80,23 @@ as described in the Web IDL specificatio
   <li>The SVG DOM requires complete support for 
   <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Views-20001113/">DOM Level 2 Views</a>
   [<a href="refs.html#ref-DOM2VIEWS">DOM2VIEWS</a>].</li>
 
   <li>The SVG DOM requires support for relevant aspects of
   <a href="http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/">DOM Level 3 Events</a>
   [<a href="refs.html#ref-DOM3EVENTS">DOM3EVENTS</a>].
   (For the specific features from DOM 3 Events that are required, see
-  see <a href="svgdom.html#RelationshipWithDOM3andUIEvents">Relationship with DOM Level 3 and UI Events</a>.)</li>
+  see <a href="svgdom.html#RelationshipWithDOM3Events">Relationship with DOM Level 3</a>.)</li>
 
   <li>The SVG DOM requires support for relevant aspects of
   <a href="http://www.w3.org/TR/2013/WD-uievents-20131105//">UI Events</a>
   [<a href="refs.html#ref-UIEVENTS">UIEVENTS</a>].
   (For the specific features from DOM 3 Events that are required, see
-  see <a href="svgdom.html#RelationshipWithDOM3andUIEvents">Relationship with DOM Level 3 and UI Events</a>.)</li>
+  see <a href="svgdom.html#RelationshipWithDOM3Events">Relationship with DOM Level 3 Events</a>.)</li>
 
   <li>For implementations that support CSS, the SVG DOM requires complete
   support for
   <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/stylesheets.html">DOM Level 2 Style Sheets</a>
   ([<a href="refs.html#ref-DOM2STYLE">DOM2STYLE</a>], chapter 1)
   and relevant aspects of
   <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/css.html">DOM Level 2 CSS</a>
   ([<a href="refs.html#ref-DOM2STYLE">DOM2STYLE</a>], chapter 2).
@@ -221,17 +221,17 @@ available for many SVG elements.</p>
 documented in this specification (see appendix <a
 href="feature.html">Feature Strings</a> for a list of features
 in the SVG language), the <strong>version</strong> number for
 the <strong>hasFeature</strong> method call is "1.1". For
 features that correspond to other languages, refer to the
 relevant other specifications to determine the appropriate
 version number for the given feature.</p>
 
-<h2 id="RelationshipWithDOM3andUIEvents">Relationship with DOM Level 3 and UI Events</h2>
+<h2 id="RelationshipWithDOM3Events">Relationship with DOM Level 3 Events</h2>
 
 <p>The SVG DOM supports select all interfaces defined in, and
 the following event types from,
 <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/">DOM Level 3 Events</a>
 [<a href="refs.html#ref-DOM3EVENTS">DOM3EVENTS</a>]:</p>
 
 <ul>
   <li>

Received on Tuesday, 17 December 2013 22:26:47 UTC