[event-timing] 各種更新

Cleanup typos and references (before larger spec change).
w3c/event-timing@f224aec

Add one more small fix that makes lychee unhappy
w3c/event-timing@f21c115

Fix broken links for Event types.
w3c/event-timing@af8a610
（和訳には織り込み済み）

＋編集（削除漏れ（ "If event’s type attribute value is not keydown nor pointerdown..."

Author: triple-underscore

event-timing-ja.html

@@ -109,17 +109,17 @@
 ●●options
 
 spec_title:Event Timing API
-spec_date:2025-05-26
-trans_update:2025-06-03
-	source_checked:
+spec_date:2026-02-24
+trans_update:2026-02-25
+source_checked:260224
 page_state_key:TIMING
 original_url:https://w3c.github.io/event-timing/
 	abbr_url:EVENT-TIMING
 spec_status:ED
 ref_id_prefix:bib-
 ref_id_lowercase:true
 conformance:w3c
-copyright:2025,permissive
+copyright:2026,permissive
 	trans_1st_pub:
 
 
@@ -429,6 +429,7 @@
 	%開始:start
 	%~event:event
 	%~window:window
+	%~window:relevantGlobal
 	%ヤリトリ~ID:interactionId
 	ヤリトリ~ID:interactiond IDs
 	ヤリトリ~ID:interactionId
@@ -453,7 +454,6 @@
 	%処理~開始:processingStart
 	%~target:target
 	%処理~終了:~processingEnd
-	%関連な大域~obj:relevantGlobal
 	%文書:doc
 	%描画~時刻印:renderingTimestamp
 	%名前:name
@@ -578,16 +578,14 @@
     Ian Clelland; Noam Rosenthal. ＜Paint Timing＞. URL: https://w3c.github.io/paint-timing/
 [PERFORMANCE-TIMELINE-2]
     Nicolas Pena Moreno. ＜Performance Timeline＞. URL: https://w3c.github.io/performance-timeline/
-[POINTEREVENTS]
-    Jacob Rossi; Matt Brubeck. ＜Pointer Events＞. URL: https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html
-[POINTEREVENTS3]
+[POINTEREVENTS4]
     Patrick Lauke; Robert Flack. ＜Pointer Events＞. URL: https://w3c.github.io/pointerevents/
 [RFC2119]
     S. Bradner. ＜Key words for use in RFCs to Indicate Requirement Levels＞. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119
 [TOUCH-EVENTS]
     Doug Schepers; et al. ＜Touch Events＞. URL: https://w3c.github.io/touch-events/
 [UIEVENTS]
-    Gary Kacmarcik; Travis Leithead. ＜UI Events＞. URL: https://w3c.github.io/uievents/
+    Xiaoqian Wu. ＜UI Events＞. URL: https://w3c.github.io/uievents/
 [WEBIDL]
     Edgar Chen; Timothy Gu. ＜Web IDL Standard＞. Living Standard. URL: https://webidl.spec.whatwg.org/
 
@@ -747,14 +745,13 @@ <h3 title="Overview">1.1. 概観</h3>
 </p>
 <ul>
 	<li>
-~event~listenerは，［
-~page読込nにおける ごく早期においては、
-まだ登録されない見込みが高い
-］ので
+~event~listenerは，
+~page読込nにおける ごく早期においては登録されていないかもしれないので
 【~targetになる要素が~instance化されるまで待機する必要がある】、
-~event~listenerを要求することは，そのような時点で~event待時間を測定することを予め除外する。
+~event~listenerを要求することは，
+~event待時間を測定することを予め除外する。
 ◎
-First, requiring event listeners precludes measuring event latency very early in the page load because listeners will likely not be registered yet at that point in time.＼
+First, requiring event listeners precludes measuring event latency very early in the page load because listeners might not be registered yet.＼
 </li>
 	<li>
 開発者は、
@@ -763,7 +760,7 @@ <h3 title="Overview">1.1. 概観</h3>
 その結果、
 ~event待時間の計算に不必要な処理能~overheadが加算される。
 ◎
-Second, developers that are only interested in the input delay might be forced to add new listeners to events that originally did not have one. This adds unnecessary performance overhead to the event latency calculation.＼
+Second, developers who are only interested in input delay might be forced to add new listeners to events that originally did not have them. This adds unnecessary performance overhead to the event latency calculation.＼
 </li>
 	<li>
 この~approachを介して［
@@ -1125,7 +1122,7 @@ <h3 title="When events are measured">1.5. ~eventは いつ測定されるか</h3
 この値は、
 粒度 8ms で供される。
 ◎
-The Event Timing API exposes a duration value, which is meant to be the time from when the physical user input occurs (estimated via the Event’s timeStamp) to the next time the rendering of the Event’s relevant global object’s associated Document’s is updated. This value is provided with 8 millisecond granularity.
+The Event Timing API exposes a duration value, which is meant to be the time from when the physical user input occurs (estimated via the Event’s timeStamp) to the next time the rendering of the Event’s relevant global object’s associated Document is updated. This value is provided with 8 millisecond granularity.
 </p>
 
 <p>
@@ -1514,7 +1511,7 @@ <h3 title="PerformanceEventTiming interface">2.1. `PerformanceEventTiming^I ~int
 この属性は、
 `結付けられた~event$が ~OR↓ を満たさない場合には 0 になる：
 ◎
-The interactionId attribute’s getter returns the ID that uniquely identifies the user interaction which triggered the associated event. This attribute is 0 unless the associated event’s type attribute value is one of:
+The interactionId attribute’s getter returns a number that uniquely identifies the user Interaction which triggered the associated event. This attribute is 0 unless the associated event’s type attribute value is one of:
 </p>
 		<ul>
 			<li>
@@ -1532,7 +1529,7 @@ <h3 title="PerformanceEventTiming interface">2.1. `PerformanceEventTiming^I ~int
 ~scrollの終了における `pointerdown$et 【？】は除外されることに注意。
 </p>
 ◎
-A pointerdown, pointerup, or click belonging to a user tap or drag. Note that pointerdown that ends in scroll is excluded.
+A pointerdown, pointerup, or click, and belongs to a tap or drag gesture. Note that pointerdown that ends in scroll is excluded.
 </li>
 			<li>
 ［
@@ -1541,7 +1538,7 @@ <h3 title="PerformanceEventTiming interface">2.1. `PerformanceEventTiming^I ~int
 利用者-~UIkeyの押下げから生じた
 ］
 ◎
-A keydown or keyup belonging to a user key press.
+A keydown or keyup, belongs to a user key press.
 </li>
 		</ul>
 	</dd>
@@ -1723,7 +1720,7 @@ <h3 title="Modifications to the HTML specification">3.2. ~HTML仕様に対する
 当の~page内で生じたヤリトリの回数
 ］用の真実を成す~sourceとして利用しなくなると見込まれる。
 ◎
-Note: the user interaction value is set to a random integer instead of 0 so that developers do not rely on it to count the number of interactions in the page. By starting at a random value, developers are less likely to use it as the source of truth for the number of interactions that have occurred in the page.
+Note: The user interaction value is set to a random integer instead of 0 so that developers do not rely on it to count the number of interactions in the page. By starting at a random value, developers are less likely to use it as the source of truth for the number of interactions that have occurred in the page.
 </p>
 	</li>
 	<li>
@@ -1927,7 +1924,7 @@ <h3 title="Should add PerformanceEventTiming">3.4. `PerformanceEventTiming^I を
 ε ならば 104 ／
 ~ELSE_ `max^op( 16, %最小~所要時間 )
 ◎
-If options is not present or if options’s durationThreshold is not present,let minDuration be 104.
+If options is not present or if options’s durationThreshold is not present, let minDuration be 104.
 ◎
 Otherwise, let minDuration be the maximum between 16 and options’s durationThreshold value.
 </li>
@@ -2208,7 +2205,7 @@ <h3 title="Computing interactionId">3.6. ヤリトリ~IDを算出する</h3>
 改変された~text内容についてではない
 ］ものを除外するために行われる。
 ◎
-Note: this check is done to exclude Events for which the type is input but that are not about modified text content.
+Note: This check is done to exclude Events for which the type is input but that are not about modified text content.
 </p>
 			</li>
 			<li>
@@ -2416,7 +2413,7 @@ <h3 title="Computing interactionId">3.6. ヤリトリ~IDを算出する</h3>
 この~algoは、
 各~eventに対応するヤリトリ~ID（ `interactionId$mET ）をアテガうよう試みる：
 ◎
-Note: the algorithm attempts to assign events to the corresponding interactiond IDs.＼
+Note: The algorithm attempts to assign events to the corresponding interaction IDs.＼
 </p>
 <ul>
 	<li>
@@ -2546,16 +2543,16 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 ⇒
 ~RET
 ◎
-If timingEntry is null, return.
+If timingEntry is null, then return.
 </li>
 	<li>
-%関連な大域~obj ~LET %~target に`関連な大域~obj$
+%~window【！relevantGlobal】 ~LET %~target に`関連な大域~obj$
 ◎
 Let relevantGlobal be target’s relevant global object.
 </li>
 	<li>
 ~IF［
-%関連な大域~obj は `Window$I を`実装-$しない
+%~window は `Window$I を`実装-$しない
 ］
 ⇒
 ~RET
@@ -2579,14 +2576,14 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 この表明は、
 この~APIが~supportする~event型たちに因り，満たされる。
 ◎
-Note: this assertion holds due to the types of events supported by the Event Timing API.
+Note: This assertion holds due to the types of events supported by the Event Timing API.
 </p>
 	</li>
 	<li>
 <p>
 %計時~entry に`結付けられた~event~target$ ~SET %~target
 ◎
-Set timingEntry’s associated eventTarget to target.
+Set timingEntry’s eventTarget to target.
 </p>
 
 <p class="note">注記：
@@ -2605,15 +2602,6 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 %計時~entry の `targetSelector$mET ~SET `~CSS選択子を生成する$( %~target )
 ◎
 Set timingEntry’s targetSelector to the result of running the algorithm to generate a CSS selector with target as input.
-</li>
-	<li>
-~IF［
-%~event の `type$m 属性の値 ~NIN { `keydown$et, `pointerdown$et }
-］
-⇒
-%関連な大域~obj の`~queueされることになる~entry群$wに %計時~entry を`付加する$
-◎
-If event’s type attribute value is not keydown nor pointerdown, append timingEntry to relevantGlobal’s entries to be queued.
 </li>
 	<li>
 <p>
@@ -2625,7 +2613,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 </p>
 		<ol>
 			<li>
-%処理待ちな~pointerdown~map ~LET %関連な大域~obj の`処理待ちな~pointerdown~map$w
+%処理待ちな~pointerdown~map ~LET %~window の`処理待ちな~pointerdown~map$w
 ◎
 Let pendingPointerDowns be relevantGlobal’s pending pointer downs.
 </li>
@@ -2643,7 +2631,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 %前回の~pointerdown~entry ~NEQ ε
 ］
 ⇒
-%関連な大域~obj の`~queueされることになる~entry群$wに %前回の~pointerdown~entry を`付加する$【！add】
+%~window の`~queueされることになる~entry群$wに %前回の~pointerdown~entry を`付加する$【！add】
 ◎
 If pendingPointerDowns[pointerId] exists:
 • Let previousPointerDownEntry be pendingPointerDowns[pointerId].
@@ -2657,7 +2645,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 			<li>
 %~window の`~contextmenuを誘発したか$w ~SET ~F
 ◎
-Set window’s is contextmenu triggered to false.
+Set relevantGlobal’s is contextmenu triggered to false.
 </li>
 		</ol>
 	</li>
@@ -2680,7 +2668,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 </p>
 				<ol>
 					<li>
-%関連な大域~obj の`~queueされることになる~entry群$wに %計時~entry を`付加する$
+%~window の`~queueされることになる~entry群$wに %計時~entry を`付加する$
 ◎
 Append timingEntry to relevantGlobal’s entries to be queued.
 </li>
@@ -2692,7 +2680,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 				</ol>
 			</li>
 			<li>
-%処理待ちな~keydown~map ~LET %関連な大域~obj の`処理待ちな~keydown~map$w
+%処理待ちな~keydown~map ~LET %~window の`処理待ちな~keydown~map$w
 ◎
 Let pendingKeyDowns be relevantGlobal’s pending key downs.
 </li>
@@ -2727,12 +2715,12 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 							<li>
 %~window の`利用者ヤリトリ値$w 値 ~INCBY ~UAにより選ばれる小さな無符号整数
 ◎
-Increase window’s user interaction value value by a small number chosen by the user agent.
+Increase relevantGlobal’s user interaction value value by a small number chosen by the user agent.
 </li>
 							<li>
 %前回の~keydown~entry の `interactionId$mET ~SET %~window の`利用者ヤリトリ値$w
 ◎
-Set previousKeyDownEntry’s interactionId to window’s user interaction value.
+Set previousKeyDownEntry’s interactionId to relevantGlobal’s user interaction value.
 </li>
 						</ol>
 
@@ -2748,7 +2736,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 					<li>
 %~window の`~queueされることになる~entry群$wに %前回の~keydown~entry を`付加する$【！add】
 ◎
-Add previousKeyDownEntry to window’s entries to be queued.
+Add previousKeyDownEntry to relevantGlobal’s entries to be queued.
 </li>
 				</ol>
 			</li>
@@ -2762,7 +2750,7 @@ <h3 title="Finalize event timing">3.8. ~event計時を完結する</h3>
 	<li>
 ~ELSE
 ⇒
-%関連な大域~obj の`~queueされることになる~entry群$w に %計時~entry を`付加する$
+%~window の`~queueされることになる~entry群$w に %計時~entry を`付加する$
 ◎
 Otherwise:
 • Append timingEntry to relevantGlobal’s entries to be queued.
@@ -2821,9 +2809,9 @@ <h3 title="Dispatch pending Event Timing entries">3.9. 処理待ちな各~event
 		</ol>
 	</li>
 	<li>
-%~window の`~queueされることになる~entry群$wを`空にする$【！clear】
+%~window の`~queueされることになる~entry群$wを`空にする$【! SET « » 】
 ◎
-Clear window’s entries to be queued.
+Set window’s entries to be queued to an empty list.
 </li>
 	<li>
 %~window の`処理待ちな~pointerdown~map$wの`値~群$mapを成す
@@ -2833,7 +2821,7 @@ <h3 title="Dispatch pending Event Timing entries">3.9. 処理待ちな各~event
 `~event計時~entryの所要時間を設定する$( %処理待ち~pointerdown~entry, %~window, %描画~時刻印 )
 ◎
 For each pendingPointerDownEntry in the values from window’s pending pointer downs:
-• Set event timing entry duration passing pendingDown, window, and renderingTimestamp.
+• Set event timing entry duration passing pendingPointerDownEntry, window, and renderingTimestamp.
 </li>
 	<li>
 %~window の`処理待ちな~keydown~map$wの`値~群$mapを成す
@@ -3043,7 +3031,7 @@ <h2 title="Security &amp; privacy considerations">4. ~security／~privacyの考
 ~web開発者には可用でなかった新たな情報
 — ~eventが処理された後に画素を描くまでの時間 —
 を導入する。
-時刻印を公開することに対する［
+時刻印を公開することに関する［
 ~security／~privacy
 ］の懸念は
 — とりわけ，この粒度の下では —
@@ -3053,7 +3041,7 @@ <h2 title="Security &amp; privacy considerations">4. ~security／~privacyの考
 これは、
 120Hz ~displayにおいても，それなりに精確な計時を許容する。
 ◎
-The duration has an 8 millisecond granularity (it is computed as such by performing rounding). Thus, a high resolution timer cannot be produced from this timestamps. However, it does introduce new information that is not readily available to web developers: the time pixels draw after an event has been processed. We do not find security or privacy concerns on exposing the timestamp, especially given its granularity. In an effort to expose the minimal amount of new information that is useful, we decided to pick 8 milliseconds as the granularity. This allows relatively precise timing even for 120Hz displays.
+The duration has an 8 millisecond granularity (it is computed as such by performing rounding). Thus, a high resolution timer cannot be produced from these timestamps. However, it does introduce new information that is not readily available to web developers: the time pixels draw after an event has been processed. We do not find security or privacy concerns with exposing the timestamp, especially given its granularity. In an effort to expose the minimal amount of new information that is useful, we decided to pick 8 milliseconds as the granularity. This allows relatively precise timing even for 120Hz displays.
 </p>
 
 <p>