Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.67f1
6000.0.58f1
6000.2.6f1
6000.3.0b3
6000.4.0a2
Issue ID
UUM-119637
Regression
No
Properties window is not closed when the GameObject is deleted and the Properties window is not focused
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Right-click the "Main Camera" GameObject in the Hierarchy window
- Click the "Properties..." button
- Dock the Properties window together with the Game View
- Click on the Game View to focus it
- Delete the "Main Camera" GameObject in the Hierarchy window
- Observe the docked Properties window
Actual results: The Properties window still exists in the Editor even when the GameObject is already deleted
Expected results: The Properties window is closed after the GameObject is deleted
Reproducible with versions: 2022.3.67f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Tested on (OS): Ubuntu 24.04, macOS Silicon Sequoia 15.6.1
Notes:
- Does not reproduce if the Properties window is focused
- Clicking on the Properties window to focus it after reproduction makes the Properties window disappear
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.