Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.39f1
Issue ID
UUM-98435
Regression
No
Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
Reproduction steps:
1. Open the attached project “ReproProject“
2. Open the scene “SampleScene“
3. Try to drag and drop the script “TestScript.cs“ from the Assets to the GameObject “GameObject” in the Hierarchy
4. Select “GameObject“ in the Hierarchy
5. Observe the result in the Inspector
Expected result: Inspector elements are rendered once
Actual result: AddComponent button is rendered twice (also the Layout Properties footer is rendered twice if a component, such as the Horizontal Layout Group, adds the footer in the Inspector), stacked on top of each other
Reproducible in: 2022.3.39f1
Not reproducible in: 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a2
Fixed in: 2022.3.40f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: The script “ComponentEditor.cs“ contains the code that triggers the issue
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.