[pointerevents] Clarify isTrusted bits in coalesced/predicted event lists w3c/pointerevents@82a6df8

＋編集（訳抜け（ "Since a trusted parent event …"

Author: triple-underscore

pointerevents-ja.html

@@ -148,9 +148,9 @@
 
 ●●options
 spec_title:Pointer Events Level 4
-spec_date:2024-08-14
-trans_update:2024-08-17
-source_checked:211206
+spec_date:2024-10-23
+trans_update:2024-10-25
+source_checked:241023
 page_state_key:UIEVENTS
 original_url:https://w3c.github.io/pointerevents/
 	abbr_url:POINTEREVENTS3
@@ -931,7 +931,6 @@
 描き:drawing:~
 塗る:paintする:~
 computing::::コンピューティング
-候補:candidate:~
 等価な:equivalent:~
 粗い:coarseな:~
 重複:duplication:~
@@ -953,6 +952,7 @@
 揃える:alignする:~
 本物の:realな:~
 広義-:inclusive::~
+集成:aggregation:~
 
 	後続して〜変化:subsequent change in
 	引き続き:subsequently
@@ -1050,6 +1050,7 @@
 	〜と同じ値をとる:match the values of
 	先行-:precede
 	一定:constant
+	変化しない:remain unchaged
 
 ●●images
 ＠pointerevents/
@@ -3183,7 +3184,6 @@ <h5 title="Suppressing a pointer event stream">4.1.3.3. ~pointer~event~streamの
 装置が~supportするより多い~pointer入力を同時に利用してヤリトリしようと試みたとき。
 ◎
 The user attempts to interact using more simultaneous pointer inputs than the device supports.
-The user inputs a greater number of simultaneous pointers than is supported by the device.
 </li>
 	<li>
 ~UAが、
@@ -4278,7 +4278,7 @@ <h2 title="Extensions to the Element interface">5. `Element^I ~interfaceに対
 — この捕捉が解放されるまでは、
 常にコレを~targetにするモノトスル。
 ◎
-Sets pointer capture for the pointer identified by the argument pointerId to the element on which this method is invoked.＼
+Set pointer capture for the pointer identified by the argument pointerId to the element on which this method is invoked.＼
 For subsequent events of the pointer, the capturing target will substitute the normal hit testing result as if the pointer is always over the capturing target, and they MUST always be targeted at this element until capture is released.＼
 </dd>
 	<dd>
@@ -4480,7 +4480,7 @@ <h2 title="Extensions to the Navigator interface">7. `Navigator^I ~interfaceに
 
 	</section>
 	<section id="declaring-direct-manipulation-behavior">
-<h2 title="Declaring candidate regions for direct manipulation behaviors">8. 直な操作の挙動~用の候補~領域の宣言-法</h2>
+<h2 title="Declaring direct manipulation behavior">8. 直な操作の挙動の宣言-法</h2>
 
 <p>
 `§ 各種 属性と既定~動作＠#attributes-and-default-actions$
@@ -4626,7 +4626,7 @@ <h3 title="The touch-action CSS property">8.1. `touch-action^p ~CSS~prop</h3>
 
 		</section>
 		<section id="determining-supported-direct-manipulation-behavior">
-<h3 title="Determining supported direct manipulation behavior">8.2. ~supportされる直な操作~用の挙動の決定-法</h3>
+<h3 title="Determining supported direct manipulation behavior">8.2. ~supportされる直な操作の挙動の決定-法</h3>
 
 <p>
 利用者が，`直な操作$による~pointer（~touchscreen上の~touchや~stylusなど）を利用して要素とヤリトリするとき、
@@ -5493,6 +5493,7 @@ <h3 title="Coalesced events">10.1. 合体された~event群</h3>
 ↓</p>
 		<ul class="switch">
 			<li>
+<p>
 `pointermove$et ／ `pointerrawupdate$et
 ⇒
 %~event の中に合体された すべての `PointerEvent$I ~objが成す連列になる。
@@ -5503,7 +5504,17 @@ <h3 title="Coalesced events">10.1. 合体された~event群</h3>
 この~listは，常に 1 個以上の~eventを包含する。
 ◎
 For trusted pointermove and pointerrawupdate events, the list is a sequence of all PointerEvents that were coalesced into this event. The "parent" trusted pointermove and pointerrawupdate event represents an accumulation of these coalesced events, but may have additional processing (for example to align with the display refresh rate). As a result, the coalesced events lists for these events always contain at least one event.＼
-</li>
+</p>
+
+<p class="note">注記：
+この場合，
+開発者は［
+%~event, %~event の`合体d~event~list$を成すすべて
+］のうち一方しか処理する必要はないはずである
+— 前者は後者の要約あるいは集成なので。
+◎
+↓</p>
+			</li>
 			<li>
 他の場合
 ⇒
@@ -5522,6 +5533,20 @@ <h3 title="Coalesced events">10.1. 合体された~event群</h3>
 </li>
 </ul>
 
+<p class="note">注記：
+ある`合体d~event~list$ %~list を包含している~trustedな~eventが~JSから配送し直されたときは、
+当の~event の `isTrusted$m は~event配送~algoにより ~F に設定されるが，
+%~list を成す各~eventの `isTrusted^m は元の値 ~T から変化しない。
+◎
+↑↑ Note
+
+Since a trusted parent event is a summary or aggregation of the coalesced events, developers should only need to process either the parent events or all of the coalesced events, but not both.
+◎
+Note
+
+When a trusted event containing a coalesced events list is re-dispatched from JavaScript, the event dispatch algorithm sets the isTrusted bit of the event to false but the same bits in the coalesced events list remain unchaged from their original true values.
+</p>
+
 <p>
 `~trusted$な`~pointer~event$ %~event の`合体d~event~list$
 — 配送された %~event に対し，その `getCoalescedEvents()$m ~methodを~callして得られるそれ —
@@ -5806,6 +5831,16 @@ <h3 title="Predicted events">10.2. 予測された~event群</h3>
 While pointerrawupdate events may have a non-empty coalesced events list, their predicted events list will, for performance reasons, usually be an empty list.
 </p>
 
+<p class="note">注記：
+ある`予測d~event~list$ %~list を包含している~trustedな~eventが~JSから配送し直されたときは、
+当の~event の `isTrusted$m は~event配送~algoにより ~F に設定されるが，
+%~list を成す各~eventの `isTrusted^m は元の値 ~T から変化しない。
+◎
+Note
+
+When a trusted event containing a predicted events list is re-dispatched from JavaScript, the event dispatch algorithm sets the isTrusted bit of the event to false but the same bits in the predicted events list remain unchaged from their original true values.
+</p>
+
 <p>
 この~listを成す~eventの個数, および［
 各~eventが現在の時刻印から どれほど離れるか
@@ -6067,8 +6102,8 @@ <h2 title="Compatibility mapping with mouse events">11. ~mouse~eventとの互換
 Regardless of their support for compatibility mouse events, the user agents MUST always support the click, auxclick and contextmenu events because these events are of type PointerEvent and are therefore not compatibility mouse events. Calling preventDefault during a pointer event MUST NOT have an effect on whether click, auxclick, or contextmenu are fired or not.
 </p>
 
-<div class="note">注記：
-<p>
+<div class="note">
+<p>注記：
 これらの高~levelな~eventのうち一部
 （ `contextmenu$et, `focus$et, `blur$et, 等々）
 と`~pointer~event$との相対的な順序は、
@@ -6082,6 +6117,8 @@ <h2 title="Compatibility mapping with mouse events">11. ~mouse~eventとの互換
 （一例として、
 ~keyboardによるヤリトリの結果として）。
 ◎
+Note
+
 The relative order of some of these high-level events (contextmenu, focus, blur, etc.) with pointer events is undefined and varies between user agents. For example, in some user agents contextmenu will often follow a pointerup, while in others it'll often precede a pointerup or pointercancel, and in some situations it may be fired without any corresponding pointer event (for instance, as a result of a keyboard interaction).
 </p>
 
@@ -6295,6 +6332,8 @@ <h3 title="Tracking the effective position of the legacy mouse pointer">11.1. 
 旧来の~mouse遷移~eventを~pointer遷移~eventより多く配送する
 ］ことが必要になる事例を次の~animationで~~説明する。
 ◎
+Note
+
 The effective position of the legacy mouse pointer models the fact that we cannot always have a direct mapping from pointer transition events (i.e., pointerover, pointerout, pointerenter and pointerleave) to corresponding legacy mouse transition events (i.e., mouseover, mouseout, mouseenter and mouseleave). The following animation illustrates a case where a user agent needs to dispatch more legacy mouse transition events than pointer transition events to be able to reconcile two primary pointers using a single legacy mouse input.
 </p>
 
@@ -6401,10 +6440,10 @@ <h3 title="Mapping for devices that support hover">11.2. ~hoverを~supportする
 ◎
 Dispatch the pointer event.
 </li>
-
 	<li>
 %装置~型 ~LET %event の `pointerType$m
-</li>
+◎
+↓</li>
 	<li>
 ~IF［
 %event の型 ~EQ `pointerdown$et
@@ -6543,7 +6582,8 @@ <h3 title="Mapping for devices that do not support hover">11.3. ~hoverを~suppor
 </li>
 	<li>
 %~pointer ~LET %event を生じさせた~pointer
-</li>
+◎
+↓</li>
 	<li>
 ~IF［
 %event の型 ~EQ `pointerover$et