--- a/src/indie-ui-events.html Fri Jan 18 14:47:45 2013 -0500
+++ b/src/indie-ui-events.html Fri Jan 18 14:50:46 2013 -0500
@@ -4,8 +4,8 @@
<meta http-equiv="Content-type" content="text/html; charset=utf-8">
<title>IndieUI: Events 1.0</title>
<link href="./css/screen.css" rel="stylesheet" type="text/css">
- <script type="text/javascript" src="./loc/en/strings.js"></script>
- <script type="text/javascript" src="./js/utils.js"></script>
+ <script type="text/javascript" src="./loc/en/strings.js" class="remove"></script>
+ <script type="text/javascript" src="./js/utils.js" class="remove"></script>
<script type="text/javascript" src="./js/respec-transformers.js" class="remove"></script>
<!--
@@ -248,7 +248,7 @@
<p>Every element may have a <code>ui-actions</code> attribute specified, which is necessary to define the <a href="#def_request_event_receiver">receiver</a> of each type of request event. The attribute, if specified, must have a value that is a set of whitespace-separated tokens representing the various actions to which the web application responds on behalf of this element. The actions that an element has assigned to it consists of all the tokens returned when the value of the <code>ui-actions</code> attribute is split on whitespace. (Duplicates are ignored.)</p>
<p>User agents MUST <a href="#def_reflected_attribute">reflect</a> the <code>ui-actions</code> content attribute in the <a href="#uiActions"><code>uiActions</code></a> IDL attribute.</p>
<div data-transform="listActions"><!-- dynamically generates event list --></div>
- <p class="ednote">We could probably combine the 'manipulation' events into a single 'manipulation' action value. I don't foresee a case where an author would want to receive some, but not all of them, and even if that case exists, the author could just not listen for those specific events.</p>
+ <!-- <p class="ednote">We could probably combine the 'manipulation' events into a single 'manipulation' action value. I don't foresee a case where an author would want to receive some, but not all of them, and even if that case exists, the author could just not listen for those specific events.</p> -->
<pre class="example">
<span class="markup" data-transform="syntaxMarkup">
<!-- body element is event listener for all events, but event receiver only for 'undo' actions. -->
@@ -393,11 +393,6 @@
<h3>Interface UIManipulationRequestEvent</h3>
<dl title="[Constructor(DOMString typeArg, optional UIManipulationRequestEventInit dictUIManipulationRequestEventInit)] interface UIManipulationRequestEvent : UIRequestEvent" class="idl">
- <!--
- <dt>readonly attribute DOMString typeArg</dt><dd>The type of event. Either one of the simple, discrete types (e.g. <code>panrequest</code>, <code>zoomrequest</code>) or the superset, continuous manipulation events.</dd>
- <dt>readonly attribute boolean canBubbleArg</dt><dd></dd>
- <dt>readonly attribute boolean cancelableArg</dt><dd></dd>
- -->
</dl>
<section id="UIManipulationRequestEventInit">
@@ -431,10 +426,10 @@
</section>
- <section id="DiscreteUIManipulationRequestEvents">
- <h4>Discrete UIManipulationRequestEvent Types</h4>
+ <section id="UIManipulationRequestEvents">
+ <h4><!-- Discrete -->UIManipulationRequestEvent Types</h4>
<p class="note">Move, Pan, and Scroll request events are functionally identical, but are specified individually to aid in authoring clarity when using similar concepts like 1) moving an object on a layout canvas, 2) panning a continuous view like a map, and 3) scrolling a scroll view.</p>
- <p>The <em>discrete</em> types of UIManipulationRequestEvents that can occur are:</p>
+ <p>The <!-- <em>discrete</em> -->types of UIManipulationRequestEvents that can occur are:</p>
<dl>
<dt id="moverequest">Move Request (<code class="event">moverequest</code>)</dt>
<dd>
@@ -486,6 +481,10 @@
</dl>
</section>
+ <p class="ednote">There may be a need for a combined, continuous manipulation events (e.g. Pan+Zoom simultaneously) in addition to the discrete events listed above, but specification ideas are incomplete. Currently an author could achieve the same result by listening for the series of discrete Zoom and Pan events.</p>
+
+<!-- Commenting the continuous events to avoid confusion, as they are not ready (for example, missing feature to associate related events, and a description of what 'canceling' implies). It's possible they may not even be necessary, given that one can get the same behavior from a series of discrete events. -->
+<!--
<section id="ContinuousUIManipulationRequestEvents">
<h4>Continuous UIManipulationRequestEvent Types</h4>
<p class="ednote">These continuous events may need an identifier per manipulation, for example, to associate a manipulationcancelrequest with the originating manipulationstartrequest that needs to be canceled.</p>
@@ -529,7 +528,7 @@
</dd>
</dl>
</section>
-
+-->
</section>
<!-- :::::::::::::::::::: END UIManipulationRequestEvent :::::::::::::::::::: -->