- From: SVG Working Group repository <cam+svgwgrepo@mcc.id.au>
- Date: Mon, 18 Nov 2013 14:03:27 -0800
- To: public-svg-wg@w3.org
details: https://svgwg.org/hg/svg2/rev/fc6f8c112a39
branches:
changeset: 555:fc6f8c112a39
user: Richard Schwerdtfeger <schwer@us.ibm.com>
date: Mon Nov 18 16:01:33 2013 -0600
description:
Begin Update to DOM3 and UI Events
diffstat:
master/interact.html | 14 +++++++-------
master/refs.html | 25 ++++++++++++++++++-------
2 files changed, 25 insertions(+), 14 deletions(-)
diffs (137 lines):
diff --git a/master/interact.html b/master/interact.html
--- a/master/interact.html
+++ b/master/interact.html
@@ -153,45 +153,45 @@ the SVG language:</p>
</tr>
</table>
</div>
<p>The following aspects of SVG are affected by events:</p>
<ul>
<li>Using <a href="svgdom.html">SVG Document Object Model (DOM)</a>, a script can
- <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-registration">register DOM 2 event listeners</a>
- ([<a href="refs.html#ref-DOM2EVENTS">DOM2EVENTS</a>], section 1.3) so that
- script can be invoked when a given event occurs.</li>
+ <a href="http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/#widl-EventTarget-addEventListener">add or remove DOM 3 event listeners</a>
+ ([<a href="refs.html#ref-DOM3EVENTS">DOM3EVENTS</a>], section 4.3 Interface Event Target) so that
+ script can be invoked or ignored when a given event occurs on an event target</li>
<li>SVG includes <a href="script.html#EventAttributes">event attributes</a>
on selected elements which define script that can be executed when a given
event occurs in association with the given element.</li>
<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>DOM2 name</em> in the second column is the name to use when
-defining <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-registration">DOM 2 event listeners</a>
-([<a href="refs.html#ref-DOM2EVENTS">DOM2EVENTS</a>], section 1.3).
+<em>DOM3 or UI 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
dispatched by the user agent. Events of those types created from script
using the <code>createEvent</code> method on the <a>Document</a> interface can be made to bubble
or be cancelable with the
-<a class='idlattr' href='http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-Event-initEvent'>initEvent</a>
+<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 2 has no keyboard events in it. The only normative spec. on this is a new <a href="https://dvcs.w3.org/hg/d4e/raw-file/default/source_respec.htm">UI events</a> specification that should become a public working draft soon. This is a replacement for the DOM 3 Events spec. The group needs to discuss the current limitation in using DOM 2 events. Also, DOMActivate does not appear in the UI Events Spec. Regarding the activate event, user agents treat click the same as activate. We should question whether we should call the table headers DOM2 name and DOM2 category. These are insufficient. Should we reference the UIEvent spec. vs. the DOM2 Event where there is overlap?
</p>
diff --git a/master/refs.html b/master/refs.html
--- a/master/refs.html
+++ b/master/refs.html
@@ -17,17 +17,17 @@
<h1>References</h1>
<h2 id="NormativeReferences">Normative references</h2>
<dl class="references">
<dt id="ref-ARIA" class="normref">[ARIA]</dt>
<dd>
- <cite class="w3crec"><a href="http://www.w3.org/TR/wai-aria-1.1/">Accessible Internet Applications (WAI-ARIA) 1.1</a></cite>,
+ <cite class="w3crec"><a href="http://www.w3.org/TR/2013/WD-wai-aria-1.1-20130926/">Accessible Internet Applications (WAI-ARIA) 1.1</a></cite>,
J. Craig, M. Cooper, eds.
World Wide Web Consortium, 26 September 2013.
<br/>This edition of WAI-ARIA 1.1 is http://www.w3.org/TR/2011/wai-aria-1.1/.
<br/>The <a href="http://www.w3.org/TR/wai-aria-1.1/">latest edition of WAI-ARIA</a> is available at
http://www.w3.org/TR/wai-aria-1.1/.
</dd>
<dt id="ref-ARIAIMPL" class="normref">[ARIAIMPL]</dt>
@@ -175,24 +175,24 @@
E. Etemad, T. Atkins, eds.
World Wide Web Consortium, 21 July 2012.
<br/>The <a href="http://dev.w3.org/csswg/css4-images/">latest edition of CSS4 Images</a> is available at
http://dev.w3.org/csswg/css4-images/.
</dd>
</dl>
<dl class="references">
- <dt id="ref-DOM2EVENTS" class="normref">[DOM2EVENTS]</dt>
+ <dt id="ref-DOM3EVENTS" class="normref">[DOM3EVENTS]</dt>
<dd>
- <cite class="w3crec"><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/">Document Object Model (DOM) Level 2 Events Specification</a></cite>,
- T. Pixley, ed.
- World Wide Web Consortium, 13 November 2000.
+ <cite class="w3crec"><a href="http://www.w3.org/TR/2013/WD-DOM-Level-3-Events-20131105/">Document Object Model (DOM) Level 3 Events Specification</a></cite>,
+ Gary Kacmarcik, Travis Leithead, Jacob Rossi, Doug Schepers, Björn Höhrmann, Philippe Le Hégaret, Tom Pixley, eds.
+ World Wide Web Consortium, 15 November 2013.
<br/>This edition of DOM 2 Events is http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/.
- <br/>The <a href="http://www.w3.org/TR/DOM-Level-2-Events/">latest edition of DOM 2 Events</a> is available at
- http://www.w3.org/TR/DOM-Level-2-Events/.
+ <br/>The <a href="http://www.w3.org/TR/DOM-Level-3-Events/">latest edition of DOM 2 Events</a> is available at
+ http://www.w3.org/TR/DOM-Level-3-Events/.
</dd>
<dt id="ref-DOM2STYLE" class="normref">[DOM2STYLE]</dt>
<dd>
<cite class="w3crec"><a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/">Document Object Model (DOM) Level 2 Style Specification</a></cite>,
C. Wilson, P. Le Hégaret, V. Apparao, eds.
World Wide Web Consortium, 13 November 2000.
<br/>This edition of DOM Level 2 Style is http://www.w3.org/TR/2000/REC-DOM-Level-2-Style-20001113/.
@@ -433,16 +433,27 @@
<dt id="ref-UAX9" class="normref">[UAX9]</dt>
<dd>
<cite><a href="http://www.unicode.org/reports/tr9/">Unicode Bidirectional Algorithm</a></cite>,
The Unicode Standard Annex #9. The Unicode Consortium, 2010.
<br />Available at http://www.unicode.org/reports/tr9/.
</dd>
+ <dt id="ref-UIEVENTS" class="normref">[UIEVENTS]</dt>
+ <dd>
+ <cite class="w3crec"><a href="http://www.w3.org/TR/2013/WD-uievents-20131105/">UI Events</a></cite>,
+ Gary Kacmarcik, Travis Leithead, eds.
+ World Wide Web Consortium, 5 November 2013.
+ <br/>This edition of UI Events is http://www.w3.org/TR/2013/WD-uievents-20131105/.
+ <br/>The <a href="http://www.w3.org/TR/uievents/">latest edition of UI Events</a> is available at
+ http://www.w3.org/TR/uievents/.
+ </dd>
+
+
<dt id="ref-UNICODE" class="normref">[UNICODE]</dt>
<dd>
<cite><a href="http://www.unicode.org/versions/Unicode6.0.0/">The Unicode Standard, Version 6.0.0</a></cite>,
The Unicode Consortium, Mountain View, CA, 2011. ISBN 978-1-936213-01-6.
<br />Available at http://www.unicode.org/versions/Unicode6.0.0.
</dd>
</dl>
Received on Monday, 18 November 2013 22:03:55 UTC