Search Issue Tracker
By Design
Votes
3
Found in
2019.3.0a8
2020.1
2020.2
2020.2.0a21
Issue ID
1275520
Regression
Yes
EventType.mouseUp not fired when the cursor is located outside of the EditorWindow
How to reproduce:
1. Open the attached '1275520.zip' project
2. Select the 'BugReport' > 'TestCode'
3. Click and hold the left mouse button in the 'TestCode' window
4. Drag the mouse pointer outside of the window
5. Release the left mouse button
Expected result: The 'EventType.MouseUp' event is fired, the text in the 'TextCode' window is updated
Actual result: The 'EventType.MouseUp' doesn't get fired
Reproducible with: 2019.3.0a8, 2020.1.0a1, 2020.1.6f1, 2020.2.0b2
Not reproducible with: 2018.4.27f1, 2019.3.0a7, 2019.4.11f1
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (2021.1.X):
MouseUp event gets fired, however it is fired only for the window where the mouse is released.
For Example: If the left click is done on window1 then MouseDown event will be fired for window1, but when a mouse click is held and released in window2 then MouseUp event will be fired for that window, i.e. where the mouse is released.