--- a/respecEdConfig.js Thu Nov 14 18:28:47 2013 +0900
+++ b/respecEdConfig.js Tue May 27 12:31:33 2014 -0700
@@ -1,7 +1,7 @@
// Configuration for the Editor's Draft of DOM Parsing and Serialization
var respecConfig = {
- specStatus: "WD",
+ specStatus: "ED",
editors: [
{
name: "Gary Kacmarcik",
@@ -10,23 +10,23 @@
companyURL: "http://www.google.com",
note: "Dec 2012 - present",
},
- {
- name: "Travis Leithead",
+ {
+ name: "Travis Leithead",
company: "Microsoft Corp.",
url: "mailto:travis.leithead@microsoft.com?subject=%5BUIEvents%5D%20Spec%20Feedback",
companyURL: "http://www.microsoft.com",
note: "Dec 2012 - present",
- }
- ],
- publishDate: "2013-11-05",
- edDraftURI: "https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm",
- previousPublishDate: "2013-07-25",
- previousMaturity: "WD",
+ }
+ ],
+ publishDate: "2014-05-27",
+ edDraftURI: "https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm",
+ previousPublishDate: "2013-07-25",
+ previousMaturity: "WD",
noIDLIn: true,
inlineCSS: true,
//noRecTrack: true,
shortName: "uievents",
- extraCSS: ["https://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
+ //extraCSS: ["https://dev.w3.org/2009/dap/ReSpec.js/css/respec.css"],
wg: ["Web Applications Working Group"],
wgURI: ["http://www.w3.org/2008/webapps/"],
wgPublicList: "www-dom",
--- a/source_respec.htm Thu Nov 14 18:28:47 2013 +0900
+++ b/source_respec.htm Tue May 27 12:31:33 2014 -0700
@@ -2,7 +2,7 @@
<html>
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>UI Events</title>
<script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
<script type="text/javascript" src="respecEdConfig.js" class='remove'></script>
@@ -12,17 +12,17 @@
<body>
<section id="abstract">
<p>This specification extends the events and features defined in DOM Events
- Level 3.</p>
+ Level 3.</p>
</section>
<section id="sotd">
- <p>Comments submitted in regard to this document should have their subject
- line prefixed with the string <q>[uievents]</q> to help facilitate
- tracking on the
- <a href="http://lists.w3.org/Archives/Public/www-dom/">www-dom
- mailing list</a>.
- There is a
- <a href="https://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&component=UI%20Events&resolution=---&list_id=20132">bug tracker</a> for this specification.</p>
+ <p>Comments submitted in regard to this document should have their subject
+ line prefixed with the string <q>[uievents]</q> to help facilitate
+ tracking on the
+ <a href="http://lists.w3.org/Archives/Public/www-dom/">www-dom
+ mailing list</a>.
+ There is a
+ <a href="https://www.w3.org/Bugs/Public/buglist.cgi?product=WebAppsWG&component=UI%20Events&resolution=---&list_id=20132">bug tracker</a> for this specification.</p>
</section>
<section id="conformance">
@@ -53,12 +53,6 @@
<p>Unless otherwise stated, string comparisons are done in a case-sensitive
manner.</p>
- <p>Implementations of this spec must also implement the following event
- constructor dictionary defined in [[!DOM4]]:</p>
-
- <ul>
- <li><code>EventInit</code></li>
- </ul>
</section>
<section id="goals">
@@ -67,11 +61,12 @@
(and also DOM4). Features in scope for this specification are:</p>
<ul>
- <li>Methods for creating and dispatching synthetic events (event constructors)</li>
<li>Additional Keyboard event properties to allow for physical key location scenarios</li>
</ul>
</section>
+ <!-- This section and its constructors have moved into DOM L3 Events
+
<section id="event-constructors">
<h1>Event Constructors</h1>
@@ -113,7 +108,7 @@
eventTarget.dispatchEvent(event);
</pre>
</div><!-- Synthesizing events - legacy -->
-
+<!--
<div class="example">
<p class="example-title">Synthesizing an untrusted event <em>using constructors</em>:
</p>
@@ -126,7 +121,7 @@
eventTarget.dispatchEvent(event);
</pre>
</div><!-- Synthesizing events - constructors -->
-
+<!--
<p>In the above example, the author only has to set the event object properties
that he or she wants. Using legacy initialization methods, such as
<code>initMouseEvent()</code>, often requires the author to specify values
@@ -272,6 +267,7 @@
<code>{ buttons: 6 }</code>
</p>
</div><!-- Initializing buttons -->
+<!--
</dd>
<dt>EventTarget? relatedTarget = null</dt>
@@ -441,9 +437,12 @@
</dl>
</section>
+-->
<section id="keyboard-events">
<h1>Keyboard Events</h1>
+<!-- 'code' has moved from UIEvents into DOM L3 Events
+
<p>The DOM Level 3 Events specification defines keyboard events that include <code>char</code> and <code>key</code>
attributes to replace the legacy keyboard event attributes <code>keycode</code> and <code>charCode</code>.
</p>
@@ -451,12 +450,16 @@
(to help identify the physical key being pressed on the keyboard) and methods to identify the <code>char</code>
associated with a given key.
</p>
-
+-->
+ <p>This section extends the KeyboardEvent interface defined in DOM Level 3 by adding methods
+ for querying the keyboard state without requiring a Keyboard event to be dispatched, and by providing locale information during the dispatch of a Keyboard event.</p>
+
<section id="keyboard-event-interface">
<h1>Interface <code>KeyboardEvent</code></h1>
<dl class="idl" title="partial interface KeyboardEvent : UIEvent">
+<!-- Moved to DOM L3 Events
<dt>readonly attribute DOMString code</dt>
<dd>
<p><code>code</code> holds a string that identifies the physical key being pressed.
@@ -466,6 +469,7 @@
<p>The un-initialized value of this attribute must be "" (the empty string).</p>
<p class="note">The <code>code</code> value for a single key will never exceed 23 bytes.</p>
</dd>
+-->
<dt>static DOMString queryKeyCap()</dt>
<dd>
@@ -561,6 +565,7 @@
</div>
</section>
+<!-- Moved to DOM L3 Events
<section id="key-codes">
<h1>Key codes</h1>
<p>A key <code>code</code> is an attribute of a keyboard event that can be used to identify the physical
@@ -639,7 +644,7 @@
is only one of each key.
</p>
</div><!-- Handling Left and Right Alt Keys -->
-
+<!--
<div class="example">
<p class="example-title">Handling the Single Quote Key
</p>
@@ -656,7 +661,7 @@
returns a consistent value.
</p>
</div><!-- Handling the Single Quote Key -->
-
+<!--
<div class="example" id="example-key-2">
<p class="example-title">Handling the '2' Key (with and without Shift pressed)
</p>
@@ -675,7 +680,7 @@
on a US keyboard always results in <code class="key-code">'Digit2'</code> in the <code>code</code> attribute.
</p>
</div><!-- Handling the 2 Key -->
-
+<!--
<div class="example" id="example-key-shift-2">
<p class="example-title">Sequence of Keyboard Events : Shift and '2'
</p>
@@ -711,7 +716,7 @@
that is not affected by the current modifier state.
</p>
</div><!-- Sequence of Keyboard Events: Shift and 2 -->
-
+<!--
</section>
<section id="keyboards">
@@ -752,7 +757,7 @@
<a href="#other-devices">Other Devices</a> section.
</p>
</section><!-- keyboard-sections -->
-
+<!--
<section id="keyboard-common-layouts">
<h1>Standard Keyboard Layouts</h1>
<p><em>This section is informative</em></p>
@@ -880,7 +885,7 @@
</section>
</section><!-- keyboard-common-layouts -->
-
+<!--
<section id="keyboard-key-codes">
<h1>Key Codes for Standard Keyboards</h1>
<p>This section describes the various keyboard sections in more detail and defines the <code>code</code>
@@ -1382,8 +1387,9 @@
</section>
</section><!-- keyboard-key-codes -->
+<!--
</section><!-- keyboards -->
-
+<!--
<section id="non-keyboards">
<h1>Non-Standard Keyboards and Other Input Devices</h1>
<p>This section briefly describes how key input from non-standard keyboards and other
@@ -1412,7 +1418,7 @@
that the button would produce when in its factory-reset condition.
</p>
</section><!-- remote-controls -->
-
+<!--
<section id="virtual-keyboards">
<h1>Virtual Keyboards</h1>
<p>When a virtual keyboard is mimicking the layout and functionality of a standard
@@ -1420,7 +1426,7 @@
Otherwise, it can leave this field blank.
</p>
</section><!-- virtual-keyboards -->
-
+<!--
<section id="chording-keyboards">
<h1>Chording Keyboards</h1>
<p>A chording keyboard is a keyboard with a small number of physical keys that requires
@@ -1434,7 +1440,7 @@
regular key events should fabricate appropriate <code>code</code> values.
</p>
</section><!-- chording-keyboards -->
-
+<!--
<section id="other-devices">
<h1>Other Devices</h1>
<p>Other devices that generate key events should be supported in the manner described above
@@ -1455,7 +1461,8 @@
should share a common prefix (like the Numpad keys).
</p>
</section><!-- other-devices -->
- </section><!-- keyboards -->
+<!--
+ </section><!-- keyboards -->
</section><!-- keyboard-events -->