--- a/master/interact.html Sun Dec 08 21:13:54 2013 +0100
+++ b/master/interact.html Tue Dec 17 16:24:20 2013 -0600
@@ -63,7 +63,7 @@
<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>
@@ -174,7 +174,7 @@
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
@@ -193,13 +193,10 @@
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>
@@ -249,7 +246,7 @@
</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>
@@ -262,7 +259,7 @@
</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>
--- a/master/struct.html Sun Dec 08 21:13:54 2013 +0100
+++ b/master/struct.html Tue Dec 17 16:24:20 2013 -0600
@@ -542,7 +542,7 @@
<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
--- a/master/svgdom.html Sun Dec 08 21:13:54 2013 +0100
+++ b/master/svgdom.html Tue Dec 17 16:24:20 2013 -0600
@@ -85,13 +85,13 @@
<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
@@ -226,7 +226,7 @@
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,