ACTION 35: Make it clearer that multiple primary pointers may be active at once
authorMatt Brubeck <mbrubeck@mozilla.com>
Tue, 09 Apr 2013 09:31:15 -0700
changeset 809e15214ee5c5
parent 79 64c74c6bd0dd
child 81 ae6a736e499e
ACTION 35: Make it clearer that multiple primary pointers may be active at once
pointerEvents.html
     1.1 --- a/pointerEvents.html	Tue Apr 09 10:57:45 2013 -0400
     1.2 +++ b/pointerEvents.html	Tue Apr 09 09:31:15 2013 -0700
     1.3 @@ -235,7 +235,7 @@
     1.4  				</dd>
     1.5  				<dt>readonly attribute boolean isPrimary</dt>
     1.6  				<dd>
     1.7 -					Indicates if the pointer represents the <a title="primary pointer" class="internalDFN">primary pointer</a>.
     1.8 +					Indicates if the pointer represents the <a title="primary pointer" class="internalDFN">primary pointer</a> of this pointer type.
     1.9  				</dd>
    1.10  			</dl>
    1.11  			<dl class="idl" title="dictionary PointerEventInit : MouseEventInit">
    1.12 @@ -282,8 +282,7 @@
    1.13  		</section>
    1.14  		<section>
    1.15  			<h2><dfn title="primary pointer">The Primary Pointer</dfn></h2>
    1.16 -			<div><p>In a multi-pointer (e.g. multi-touch) scenario, the primary pointer is used to identify a master pointer amongst the set of active pointers.  This pointer is the one that will produce <a title="compatibility mouse events" class="internalDFN">compatibility mouse events</a>. It is also useful when single-pointer interaction is desired by an author.</p>
    1.17 -			<p>The primary pointer is indicated on events by a value of <code>true</code> for the <a href="#widl-PointerEvent-isPrimary"><code>isPrimary</code></a> property.</div>
    1.18 +			<div><p>In a multi-pointer (e.g. multi-touch) scenario, the <a href="#widl-PointerEvent-isPrimary"><code>isPrimary</code></a> property is used to identify a master pointer amongst the set of active pointers for each event type.  Only a primary pointer will produce <a title="compatibility mouse events" class="internalDFN">compatibility mouse events</a>. Authors who desire single-pointer interaction can achieve this by ignoring non-primary pointers.
    1.19  			<section>
    1.20  				<h3>Determining the primary pointer</h3>
    1.21  				<div>When dispatching a pointer event, a pointer is considered primary if:
    1.22 @@ -298,7 +297,7 @@
    1.23  					<dt>primary pen input</dt><dd>A pointer representing pen input is considered the <i>primary pen input</i> if its <code>pointerdown</code> event was dispatched when no other active pointers representing pen input existed.</dd>
    1.24  				</dl>
    1.25  				<div class="note">When two or more pointer device types are being used concurrently, multiple pointers are considered primary. For example, a touch contact and a mouse cursor moved simultaneously will produce pointers that are both considered primary.</div>
    1.26 -				<div class="note">In some platforms, the primary pointer is determined using all active pointers on the device including those not targeted at the user agent (e.g. in another application). This means it is possible for the user agent to fire pointer events in which no pointer is marked as the primary pointer.  For example, if the first touch interaction is targeted outside the user agent and a secondary (multi-touch) touch interaction is targeted inside the user agent, then the user agent fires pointer events for the second contact with a value of <code>false</code> for <code>isPrimary</code>.</div>
    1.27 +				<div class="note">In some platforms, the primary pointer is determined using all active pointers on the device, including those not targeted at the user agent (e.g. in another application). This means it is possible for the user agent to fire pointer events in which no pointer is marked as a primary pointer.  For example, if the first touch interaction is targeted outside the user agent and a secondary (multi-touch) touch interaction is targeted inside the user agent, then the user agent may fire pointer events for the second contact with a value of <code>false</code> for <code>isPrimary</code>.</div>
    1.28  				
    1.29  			</section>
    1.30  		</section>
    1.31 @@ -777,4 +776,4 @@
    1.32  	</section>
    1.33  	<!-- appendix -->
    1.34    </body>
    1.35 -</html>
    1.36 \ No newline at end of file
    1.37 +</html>