Update CHANGELOG.md

Author: photonstorm

CHANGELOG.md

@@ -4,13 +4,23 @@
 
 ### Input System Changes
 
+#### Input System Bug Fixes
+
+* Calling `setPollAlways()` would cause the `'pointerdown'` event to fire multiple times. Fix #4541 (thanks @Neyromantik)
+* The pointer events were intermittently not registered, causing `pointerup` to often fail. Fix #4538 (thanks @paulsymphony)
+* Due to a regression in 3.16 the drag events were not performing as fast as before, causing drags to feel lagged. Fix #4500 (thanks @aliblong)
+* Over and Out events now work for any number of pointers in multi-touch environments, not just the first touch pointer registered. They also now fire correctly on touch start and touch end / cancel events.
+
+#### Input System API Changes
+
 The old 'input queue' legacy system, which was deprecated in 3.16, has been removed entirely in order to tidy-up the API and keep input events consistent. This means the following changes:
 
 * Removed the `inputQueue` Game config property.
 * Removed the `useQueue`, `queue` and `_updatedThisFrame` properties from the Input Manager.
 * Removed the `legacyUpdate` and `update` methods from the Input Manager.
 * Removed the `ignoreEvents` property as this should now be handled on a per-event basis.
 * The Input Manager no longer listens for the `GameEvents.POST_STEP` event.
+* The following Input Manager methods no longer require the `time` argument, as it's taken from the event timeStamp: `startPointer`, `updatePointer`, `stopPointer` and `cancelPointer`. All of these methods also now calculate the pointer motion updates.
 
 As a result, all of the following Input Manager methods have been renamed:
 
@@ -22,7 +32,7 @@ As a result, all of the following Input Manager methods have been renamed:
 * `queueMouseMove` is now called `onMouseMove` and invoked by the Mouse Manager.
 * `queueMouseUp` is now called `onMouseUp` and invoked by the Mouse Manager.
 
-Each of these handlers used to check the `enabled` state of the Input Manager, but this now handled directly in the Touch and Mouse Managers instead, leading to less branching and cleaner tests.
+Each of these handlers used to check the `enabled` state of the Input Manager, but this now handled directly in the Touch and Mouse Managers instead, leading to less branching and cleaner tests. They also all used to run an IIFE that updated motion on the changed pointers array, but this is now handled directly in the event handler, allowing it to be removed from here.
 
 Because the legacy queue mode is gone, there is no longer any need for the DOM Callbacks:
 
@@ -41,6 +51,8 @@ The following changes took place in the Input Plugin class:
 * `processDragUpEvent` is a new method that handles an up event for drag enabled Game Objects.
 * `processDragStartList` is a new internal method that builds a drag list for a pointer.
 * `processDragThresholdEvent` is a new internal method that tests when a pointer with drag thresholds can drag.
+* `processOverEvents` is a new internal method that handles when a touch pointer starts and checks for over events.
+* `processOutEvents` is a new internal method that handles when a touch pointer stops and checks for out events.
 
 The following changes took place in the Pointer class:
 
@@ -49,14 +61,10 @@ The following changes took place in the Pointer class:
 * `Pointer.justUp` has been removed as it's not used internally and makes no sense under the DOM event system.
 * `Pointer.justMoved` has been removed as it's not used internally and makes no sense under the DOM event system.
 * The `Pointer.reset` method has been removed as it's no longer required internally.
-
-#### Input System Bug Fixes
-
-* Calling `setPollAlways()` would cause the `'pointerdown'` event to fire multiple times. Fix #4541 (thanks @Neyromantik)
-* The pointer events were intermittently not registered, causing `pointerup` to often fail. Fix #4538 (thanks @paulsymphony)
-* Due to a regression in 3.16 the drag events were not performing as fast as before, causing drags to feel lagged. Fix #4500 (thanks @aliblong)
-* Over and Out events should now work for any pointer in multi-touch environments, not just the first touch pointer registered.
-
+* `Pointer.touchstart` now has two arguments, the Touch List entry and the Touch Event. The full Touch Event is now stored in `Pointer.event` (instead of the Touch List entry).
+* `Pointer.touchmove` now has two arguments, the Touch List entry and the Touch Event. The full Touch Event is now stored in `Pointer.event` (instead of the Touch List entry).
+* `Pointer.touchend` now has two arguments, the Touch List entry and the Touch Event. The full Touch Event is now stored in `Pointer.event` (instead of the Touch List entry).
+* `Pointer.touchcancel` now has two arguments, the Touch List entry and the Touch Event. The full Touch Event is now stored in `Pointer.event` (instead of the Touch List entry).
 
 ### New Features