Search Issue Tracker
Duplicate
Votes
4
Found in
2021.2.0b6
2022.1
Issue ID
1356362
Regression
Yes
Input System detects PointerMove event after PointerDown events in WebGL builds
Reproduction steps:
1. Open the attached "BrowserInputBugRepro.zip" project
2. Load "SampleScene" in the Assets/Scenes folder
3. Enter Play Mode
4. Click anywhere in the Game View and observe the text
5. Exit Play mode and make sure the WebGL platform is selected in the Build Settings
6. Build and Run the project
7. Click anywhere in the build and observe the text
Expected result: PointerMove event after "PointerDown performed" and "PointerDown Cancelled" events is not detected. The Pointer coordinates after "PointerDown performed" are correct.
Actual result: PointerMove events after PointerDown events are detected. The coordinates after "PointerDown performed" are incorrect.
Reproducible with: 2021.2.0b6, 2021.2.0b7, 2022.1.0a5
Not reproducible with: 2020.3.16f1, 2021.1.17f1, 2021.2.0a17
Could not test with: 2019.4.29f1, 2021.2.0a18, 2021.2.0b5 (build fails)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
This is a duplicate of issue #1347311