update comment

ritamerkl · web-flow · commit 51b96434b7fb · 2025-02-19T10:16:59.000+01:00
diff --git a/Packages/com.unity.inputsystem/InputSystem/Plugins/UI/InputSystemUIInputModule.cs b/Packages/com.unity.inputsystem/InputSystem/Plugins/UI/InputSystemUIInputModule.cs
@@ -895,7 +895,7 @@ internal void ProcessNavigation(ref NavigationModel navigationState)
             // Process submit and cancel events.
             if (!usedSelectionChange && eventSystem.currentSelectedGameObject != null)
             {
-                // NOTE: Whereas we use callbacks for the other actions, we rely on WasPressedThisFrame() for
+                // NOTE: Whereas we use callbacks for the other actions, we rely on WasPerformedThisRenderingFrame() for
                 //       submit and cancel. This makes their behavior inconsistent with pointer click behavior where
                 //       a click will register on button *up*, but consistent with how other UI systems work where
                 //       click occurs on key press. This nuance in behavior becomes important in combination with

Original file line number	Diff line number	Diff line change
`@@ -895,7 +895,7 @@ internal void ProcessNavigation(ref NavigationModel navigationState)`
`895`	`895`	`// Process submit and cancel events.`
`896`	`896`	`if (!usedSelectionChange && eventSystem.currentSelectedGameObject != null)`
`897`	`897`	`{`
`898`		`- // NOTE: Whereas we use callbacks for the other actions, we rely on WasPressedThisFrame() for`
	`898`	`+ // NOTE: Whereas we use callbacks for the other actions, we rely on WasPerformedThisRenderingFrame() for`
`899`	`899`	`// submit and cancel. This makes their behavior inconsistent with pointer click behavior where`
`900`	`900`	`// a click will register on button up, but consistent with how other UI systems work where`
`901`	`901`	`// click occurs on key press. This nuance in behavior becomes important in combination with`