Search Issue Tracker
Fixed
Fixed in 2021.3.44f1, 2022.3.45f1, 6000.0.16f1, 7000.0.0a1
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.3.0b9
6000.0.0b11
Issue ID
UUM-65367
Regression
No
The Mouse click Action Phase is set to "Canceled" when the Cursor is locked and the Mouse is moved with the Left Mouse click held in a WebGL build
How to reproduce
1. Open the “WebGLPhaseBug.zip“ project
2. Go to “Build Settings…” in the “File” tools
3. Enable the “Development Build“ checkbox
4. Click the "Build And Run” button
5. After building and running the Player, open the Web Developer Tools panel in the browser (F12)
6. Click and hold the Left Mouse Button in the Game view
7. While holding the Left Mouse Button, move the Mouse
8. Observe the Console in the Web Developer Tools panel
Expected results: The Action Phase gets assigned the status “Canceled“ on the Left Mouse Button release
Actual results: The Action Phase gets assigned the status “Canceled“ when the Mouse is moved
Reproducible in: 2021.3.35f1, 2022.3.20f1, 2023.3.0b9
Could not test in: 2023.2.12f1 (NullRefferenceException Errors in the RenderPipeline while building)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Note: Reproducible in the WebGL Player only
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note (fix version 6000.0.16f1):
Thank you for taking the time to report this issue. After investigating, the engineering team determined this was a legitimate bug which has been fixed.
Resolution Note (fix version 2022.3.45f1):
Thank you for taking the time to report this issue. After investigating, the engineering team determined this was a legitimate bug which has been fixed.