--- a/html/DOM3-Events.html Mon May 12 17:25:01 2014 -0700
+++ b/html/DOM3-Events.html Wed May 14 17:50:42 2014 -0700
@@ -757,7 +757,7 @@
<dt>const unsigned short NONE = 0</dt>
<dd>
- <p>The current event is not being dispatched, i.e., the <a href="#widl-Event-eventPhase">Event.eventPhase</a> is being observered prior to
+ <p>The current event is not being dispatched, i.e., the <a href="#widl-Event-eventPhase"><code>Event.eventPhase</code></a> is being observed prior to
calling <a href="#widl-EventTarget-dispatchEvent">EventTarget.dispatchEvent()</a> or following the completion of the
<a class="def" href="#glossary-phase">event phases</a> of a given <code>Event</code>.</p>
</dd>
@@ -1076,7 +1076,7 @@
<code>type</code>, <code>listener</code>, and <code>useCapture</code> has no effect. Doing so does not cause the event listener to be registered more than once and
does not cause a change in the triggering order.</p>
- <p class="note"><strong>Note:</strong> In addition to the <a href="#widl-EventTarget-addEventListener">EventTarget.addEventListener</a> method, some
+ <p class="note"><strong>Note:</strong> In addition to the <a href="#widl-EventTarget-addEventListener"><code>EventTarget.addEventListener</code></a> method, some
<a class="def" href="#glossary-host-language">host languages</a> allow a content author to register event listeners by the use of attributes, e.g.,
<code>onclick="handleClick()"</code> (see [<cite><a class="informative" href="#references-HTML5">HTML5</a></cite>] for further examples). Due to the
language-specific details, this type of event listener registration is not defined in this specification. In general, many event types can be used as an attribute
@@ -1108,7 +1108,7 @@
If <code>listener</code> is a function then it MUST be used as the callback for the event.
Otherwise, if <code>listener</code> implements
<a href="#interface-EventListener"><code>EventListener</code></a>, then its
- <a href="#widl-EventListener-handleEvent">handleEvent</a> method MUST be used as the callback.
+ <a href="#widl-EventListener-handleEvent"><code>handleEvent</code></a> method MUST be used as the callback.
</p>
<p>If null is passed for the <code>listener</code>, then <code>addEventListener</code> does nothing.
</p>
@@ -1121,7 +1121,7 @@
href="#glossary-bubbling-phase"> bubbling</a> phase. If <code>false</code>, the event listener MUST only be triggered during the <a class="def"
href="#glossary-target-phase">target</a> and <a class="def" href="#glossary-bubbling-phase">bubbling</a> phases.</p>
- <p>This parameter MUST be optional. If not provided, the <a href="#widl-EventTarget-addEventListener">EventTarget.addEventListener</a> method MUST behave as if
+ <p>This parameter MUST be optional. If not provided, the <a href="#widl-EventTarget-addEventListener"><code>EventTarget.addEventListener</code></a> method MUST behave as if
<code class="parameter-name">useCapture</code> was specified to be <code>false</code>.</p>
<p class="note"><strong>Authoring Note:</strong> The <code class="parameter-name">useCapture</code> parameter was mandatory in
@@ -1158,7 +1158,7 @@
this represents two unique registrations. Removal of an event listener registered for the capture and target phases does not affect the same event listener registered
for the target and bubbling phases, and vice versa.</p>
- <p>This parameter MUST be optional. If not provided, the <a href="#widl-EventTarget-removeEventListener">EventTarget.removeEventListener</a> method MUST behave as if
+ <p>This parameter MUST be optional. If not provided, the <a href="#widl-EventTarget-removeEventListener"><code>EventTarget.removeEventListener</code></a> method MUST behave as if
<code class="parameter-name">useCapture</code> were specified to be <code>false</code>.</p>
<p class="note"><strong>Authoring Note:</strong> The <code class="parameter-name">useCapture</code> parameter was mandatory in
@@ -1212,8 +1212,8 @@
<p>The <code>EventListener</code> interface is the primary way to handle events. <code>EventListener</code> represents the callback object that the user agent will
invoke when dispatching an <code>Event</code> to an <a href="#interface-EventTarget"><code>EventTarget</code></a>.</p>
- <p class="note"><strong>Note:</strong> Authors define an object which implements the <code>EventListener</code> interface and register their event listener using <a
- href="#widl-EventTarget-addEventListener">EventTarget.addEventListener</a>. In JavaScript, an <code>EventListener</code> can be either a function or an object
+ <p class="note"><strong>Note:</strong> Authors define an object which implements the <code>EventListener</code> interface and register their event listener using
+ <a href="#widl-EventTarget-addEventListener"><code>EventTarget.addEventListener</code></a>. In JavaScript, an <code>EventListener</code> can be either a function or an object
with a <code>handleEvent</code> member function.</p>
<p class="note"><strong>Note:</strong> It is a best practice for authors to remove their <code>EventListener</code> from its <a href="#interface-EventTarget"><code>EventTarget</code></a>
@@ -2494,7 +2494,7 @@
<p class="note" id="_9"><strong>Note:</strong> When using this event type, the content author can use the event's <code class="attribute-name"><a href="#widl-FocusEvent-relatedTarget">
FocusEvent.relatedTarget</a></code> attribute (or a host-language-specific method or means) to get the currently focused element before the focus shifts to the
next focus <a class="def" href="#glossary-event-target">event target</a>, thus having access to both the element losing focus and the element gaining focus
- without the use of the <a class="eventtype" href="#event-type-blur"><code>blur</code></a> or <a class="eventtype" href="#event-type-focusout">focusout</a> event
+ without the use of the <a class="eventtype" href="#event-type-blur"><code>blur</code></a> or <a class="eventtype" href="#event-type-focusout"><code>focusout</code></a> event
types.</p>
</dd>
</dl>
@@ -2855,34 +2855,32 @@
<dt>boolean ctrlKey = false</dt>
<dd>
- <p>Initializes the <code>ctrlKey</code> attribute of the MouseEvent
- object to <code>true</code> if the <code>ctrlKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ <p>Initializes the <code>altKey</code> attribute of the MouseEvent
+ object to <code>true</code> if the <code class="key">'Control'</code>
+ (control) key modifier is to be considered active,
+ <code>false</code> otherwise.</p>
</dd>
<dt>boolean shiftKey = false</dt>
<dd>
<p>Initializes the <code>shiftKey</code> attribute of the MouseEvent
- object to <code>true</code> if the <code>shiftKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ object to <code>true</code> if the <code class="key">'Shift'</code>
+ key modifier is to be considered active, <code>false</code> otherwise.</p>
</dd>
<dt>boolean altKey = false</dt>
<dd>
<p>Initializes the <code>altKey</code> attribute of the MouseEvent
- object to <code>true</code> if the <code>altKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ object to <code>true</code> if the <code class="key">'Alt'</code>
+ (alternative) (or <code class="glyph">'Option'</code>) key modifier
+ is to be considered active, <code>false</code> otherwise.</p>
</dd>
<dt>boolean metaKey = false</dt>
<dd>
<p>Initializes the <code>metaKey</code> attribute of the MouseEvent
- object to <code>true</code> if the <code>metaKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ object to <code>true</code> if the <code class="key">'Meta'</code>
+ key modifier is to be considered active, <code>false</code> otherwise.</p>
</dd>
<dt>short button = 0</dt>
@@ -4810,7 +4808,7 @@
<dt>readonly attribute boolean shiftKey</dt>
<dd>
- <p><code>true</code> if the shift (<code class="key">Shift</code>) key modifier was active.</p>
+ <p><code>true</code> if the shift (<code class="key">'Shift'</code>) key modifier was active.</p>
<p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
</dd>
@@ -4838,7 +4836,7 @@
<a class="eventtype" href="#event-type-beforeinput"><code>beforeinput</code></a>,
<a class="eventtype" href="#event-type-input"><code>input</code></a>
in this order, at a rate determined by the system configuration. For mobile devices which have <em>long-key-press</em>
- behavior, the first key event with a <a href="#widl-KeyboardEvent-repeat">repeat</a> attribute value of <code>'true'</code> MUST serve as an
+ behavior, the first key event with a <a href="#widl-KeyboardEvent-repeat"><code>repeat</code></a> attribute value of <code>'true'</code> MUST serve as an
indication of a <em>long-key-press</em>. The length of time that the key MUST be pressed in order to begin repeating is configuration-dependent.</p>
<p>The <a class="def" href="#glossary-un-initialized-value">un-initialized value</a> of this attribute MUST be <code>false</code>.</p>
@@ -4921,34 +4919,32 @@
<dt>boolean ctrlKey = false</dt>
<dd>
- <p>Initializes the <code>ctrlKey</code> attribute of the KeyboardEvent
- object. This attribute should be set to <code>true</code> if the <code>ctrlKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ <p>Initializes the <code>altKey</code> attribute of the KeyboardEvent
+ object to <code>true</code> if the <code class="key">'Control'</code>
+ (control) key modifier is to be considered active,
+ <code>false</code> otherwise.</p>
</dd>
<dt>boolean shiftKey = false</dt>
<dd>
<p>Initializes the <code>shiftKey</code> attribute of the KeyboardEvent
- object. This attribute should be set to <code>true</code> if the <code>shiftKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ object to <code>true</code> if the <code class="key">'Shift'</code>
+ key modifier is to be considered active, <code>false</code> otherwise.</p>
</dd>
<dt>boolean altKey = false</dt>
<dd>
<p>Initializes the <code>altKey</code> attribute of the KeyboardEvent
- object. This attribute should be set to <code>true</code> if the <code>altKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ object to <code>true</code> if the <code class="key">'Alt'</code>
+ (alternative) (or <code class="glyph">'Option'</code>) key modifier
+ is to be considered active, <code>false</code> otherwise.</p>
</dd>
<dt>boolean metaKey = false</dt>
<dd>
<p>Initializes the <code>metaKey</code> attribute of the KeyboardEvent
- object. This attribute should be set to <code>true</code> if the <code>metaKey</code> modifier
- key is to be considered depressed, <code>false</code> otherwise.
- </p>
+ object to <code>true</code> if the <code class="key">'Meta'</code>
+ key modifier is to be considered active, <code>false</code> otherwise.</p>
</dd>
<dt>boolean repeat = false</dt>
@@ -5100,7 +5096,8 @@
<a class="def" href="#glossary-host-language">host language</a> to accept keyboard input
for non-text purposes, such as the activation of an accelerator key or trigger of some
other behavior. If no suitable element is in focus, the event target will be the HTML
- <body> element if available, otherwise the <a href="#glossary-root-element">root element</a>.
+ <a href="#glossary-body-element">body element</a> if available,
+ otherwise the <a href="#glossary-root-element">root element</a>.
</p>
<p class="note"><strong>Note:</strong>
@@ -5161,8 +5158,9 @@
<td>
<ul>
<li><a href="#widl-Event-target"><code class="attribute-name">Event.target</code></a>:
- focused element processing the key event or if no element focused, then the <body>
- element if available, otherwise the <a href="#glossary-root-element">root element</a></li>
+ focused element processing the key event or if no element focused, then the
+ <a href="#glossary-body-element">body element</a> if available, otherwise the
+ <a href="#glossary-root-element">root element</a></li>
<li><a href="#widl-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>:
<a class="def" href="#glossary-window"><code>Window</code></a></li>
<li><a href="#widl-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>:
@@ -5272,8 +5270,9 @@
<td>
<ul>
<li><a href="#widl-Event-target"><code class="attribute-name">Event.target</code></a>:
- focused element processing the key event or if no element focused, then the <body>
- element if available, otherwise the <a href="#glossary-root-element">root element</a></li>
+ focused element processing the key event or if no element focused, then the
+ <a href="#glossary-body-element">body element</a> if available, otherwise the
+ <a href="#glossary-root-element">root element</a></li>
<li><a href="#widl-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>:
<a class="def" href="#glossary-window"><code>Window</code></a></li>
<li><a href="#widl-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>:
@@ -6372,7 +6371,7 @@
</tbody>
</table>
<p>Regardless of the current locale or the modifier key state, pressing the key labelled <code class="glyph">'2'</code>
- on a US keyboard always results in <code class="key">'Digit2'</code> in the <code>code</code> attribute.
+ on a US keyboard always results in <code class="code">'Digit2'</code> in the <code>code</code> attribute.
</p>
</div><!-- Handling the 2 Key -->
@@ -6754,7 +6753,7 @@
</div>
<p>The following example describes an alternate sequence of keys to the example above, where the <code class="key">'Shift'</code> key is released before the <code
- class="key">'Q'</code> key. The key value for the key labeled <code class="key">'Q'</code> will revert to its unshifted value for the <a class="eventtype" href="#event-type-keyup">
+ class="key">'Q'</code> key. The key value for the key labeled <code class="glyph">'Q'</code> will revert to its unshifted value for the <a class="eventtype" href="#event-type-keyup">
<code>keyup</code></a> event:</p>
<div class="example">
@@ -6983,7 +6982,7 @@
</p>
<p>In some cases, modifier keys change the key value value for a key event.
- For example, on some MacOS keyboards, the key labeled <code>'delete'</code>
+ For example, on some MacOS keyboards, the key labeled <code class="glyph">'delete'</code>
functions the same as the <code class="key">'Backspace'</code> key on the
Windows OS when unmodified, but when modified by the <code class="key">'Fn'</code>
key, acts as the <code class="key">'Delete'</code> key, and the value of the
@@ -9204,8 +9203,9 @@
<td>
<ul>
<li><a href="#widl-Event-target"><code class="attribute-name">Event.target</code></a>:
- focused element processing the key event or if no element focused, then the <body>
- element if available, otherwise the <a href="#glossary-root-element">root element</a></li>
+ focused element processing the key event or if no element focused, then the
+ <a href="#glossary-body-element">body element</a> if available, otherwise the
+ <a href="#glossary-root-element">root element</a></li>
<li><a href="#widl-UIEvent-view"><code class="attribute-name">UIEvent.view</code></a>:
<a class="def" href="#glossary-window"><code>Window</code></a></li>
<li><a href="#widl-UIEvent-detail"><code class="attribute-name">UIEvent.detail</code></a>:
@@ -10582,6 +10582,10 @@
content that uses the interfaces, events, and event flow defined in this specification. See <a href="#conf-authors">Content authors and content</a> conformance
category for more details.</dd>
+ <dt id="glossary-body-element"><dfn>body element</dfn></dt>
+ <dd>In HTML or XHTML documents, the body element represents the contents of the document. In a well-formed HTML document, the body element is a first descendant of
+ the <a href="#glossary-root-element">root element</a>.
+
<dt id="glossary-bubbling-phase"><dfn>bubbling phase</dfn></dt>
<dd>The process by which an <a class="def" href="#glossary-event">event</a> can be handled by one of the target's ancestors <em>after</em> being handled by the
<a class="def" href="#glossary-event-target">event target</a>. See the description of the <a href="#bubble-phase">bubble phase</a> in the context
@@ -10618,7 +10622,7 @@
<dt id="glossary-dead-key"><dfn>dead key</dfn></dt>
<dd>A dead key is a key or combination of keys which produces no character by itself, but which in combination or sequence with another key produces a modified character,
- such as a character with diacritical marks (e.g., <code>ö</code>, <code>é</code>, <code>â</code>).</dd>
+ such as a character with diacritical marks (e.g., <code class="key">ö</code>, <code class="key">é</code>, <code class="key">â</code>).</dd>
<dt id="glossary-default-action"><dfn>default action</dfn></dt>
<dd>A <a class="def" href="#glossary-default-action">default action</a> is an OPTIONAL supplementary behavior that an implementation
--- a/html/spec-WD.css Mon May 12 17:25:01 2014 -0700
+++ b/html/spec-WD.css Wed May 14 17:50:42 2014 -0700
@@ -5,7 +5,7 @@
color: #005A9C;
}
-.attribute-name {
+/*.attribute-name {
color: black;
background-color: #FFFFD2;
}
@@ -25,7 +25,7 @@
.parameter-name {
color: black;
background-color: #FEE6F8;
-}
+}*/
/* Some fun IDL styling */
.comment {
@@ -37,15 +37,15 @@
font-size: larger;
}
-ul.toc, ol.toc {list-style: none}
+/*ul.toc, ol.toc {list-style: none}
div.toc ul ul, div.toc ol ol {margin-left: 0}
div.toc ul ul ul, div.toc ol ol ol {margin-left: 1em}
div.toc ul ul ul ul, div.toc ol ol ol ol {margin-left: 0}
li.tocline1 {font-weight: bold}
li.tocline2 {font-weight: normal}
li.tocline4 {font-style: italic}
-
-code { font-family: monospace }
+*/
+/* code { font-family: monospace } */
div.paramtable { margin-left: 1em }
div.returntable { margin-left: 1em }
@@ -92,14 +92,15 @@
}
.event-definition dfn a {
- font-family: monospace;
+ font-size: larger;
+ /*font-family: monospace;
color: black;
font-weight: normal;
font-style: normal;
padding-left: 1em;
padding-right: 1em;
padding-top: 0.2em;
- background-color: #FFC500;
+ background-color: #FFC500;*/
}
.event-definition dd table {
@@ -107,9 +108,9 @@
}
/* Added the d3-idl class here to remove underlines in IDL blocks */
-.event-definition a, .d3-idl a {
+/*.event-definition a, .d3-idl a {
text-decoration: none
-}
+}*/
.event-definition td b {
font-weight: normal
@@ -160,12 +161,12 @@
border-left-style: solid;
}
-h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
+/*h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
color: inherit !important;
font-weight: inherit !important;
text-decoration: none !important;
font-style: inherit !important;
-}
+}*/
.typeCell {
background-color: #cfcfcf;
@@ -180,14 +181,14 @@
font-weight: bold;
}
-a.eventtype {
+/*a.eventtype {
text-decoration: none;
-}
+}*/
-a.eventtype code {
+/*a.eventtype code {
font-size: 1.13em;
color: #ff6d00;
-}
+}*/
/* Denotes a key value (the value of the KeyboardEvent.key property) */
.key {
@@ -220,7 +221,7 @@
a.def {
color: inherit;
text-decoration: inherit;
- border-bottom: 1.8px dashed blue;
+ border-bottom: 1px dotted blue;
}
/*style for table-event-summary and table-key-values */