If you destroyed a Game Object that had a custom cursor set during one of its input events the cursor didn't correctly reset. Fix phaserjs#4033

Author: photonstorm

CHANGELOG.md

@@ -106,6 +106,7 @@ Doing this gives you the ability to modify the texture before this happens, allo
 * The WebGL Renderer now always enables the `SCISSOR_TEST`, this allows Game Objects that use the scissor (such as custom objects, or Bitmap Text) to render properly again.
 * The Cameras `setScene` method, which is called automatically when a new Camera is created, will now call `updateSystem` which correctly increases the custom viewport counter. This fixes an issue with mini-cams inside of larger cameras not clipping their contents properly. If a Camera is moved to another Scene it also now correctly shrinks the total custom viewport counter.
 * Due to the two fixes above another bug was fixed: The ability for you to swap between Cameras with and without `setRenderToTexture` enabled with custom shaders. Previously if you used this with a custom shader then only the first Camera using the shader would render, the rest would appear black. Now, all Cameras using the custom shader work correctly. As a result all of the 'experimental' Camera rendering properties from 3.12 have been moved to stable.
+* If you destroyed a Game Object that had a custom cursor set during one of its input events the cursor didn't correctly reset. Fix #4033 (thanks @pantoninho)
 
 ### Examples, Documentation and TypeScript
 

src/input/InputPlugin.js

@@ -595,6 +595,8 @@ var InputPlugin = new Class({
         input.hitAreaCallback = undefined;
         input.callbackContext = undefined;
 
+        this.manager.resetCursor(input);
+
         gameObject.input = null;
 
         //  Clear from _draggable, _drag and _over