Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a11
2019.1.9f1
2019.2.0a1
2019.3.0a1
Issue ID
1169217
Regression
No
ObjectField Object doesn't detect double clicking when its value is set
Repro steps:
1. Open attached "case_1169217.zip"
2. Click on the "BugReport" in Editor, at the top left of the screen
3. Click on "Test"
4. Double click on "New Game Object" in the pop-up window
Expected results: both clicks are detected and printed by the Console
Actual results: only the first click is detected and printed by the Console
Reproducible with: 2019.1.11f1, 2019.2.0b10, 2019.3.0a2
Could not test with: 2019.1.0a10 and earlier due to scripting errors, 2019.3.0a3 and later due to being unable to assign a Game Object to the Object Field
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.3.X):
low priority and unlikely to be resolved for the moment.