Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.6.1
Issue ID
ISXB-574
Regression
No
Player Input component Events foldout gets collapsed when reselecting the GameObject
Reproduction steps:
1. Open the “Foldouts“ project
2. Open the “Sample” scene
3. Select the “PlayerInput“ GameObject
4. Expand the “Events” foldout in Inspector
5. Reselect the “PlayerInput” GameObject
Expected result: The “Events” foldout is expanded
Actual result: The “Events” foldout is collapsed
Reproduced in: 0.1.2-preview (2021.1.0a1), 1.6.1 (2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23)
Reproduced using: macOS 13.4.1 (Intel), Windows 10
Notes:
1. Also reproduced with the Player Input Manager component
2. Not reproduced with other components (e.g. Rigidbody)
3. !!! Alt/Option + Click does not fully expand/collapse the “Events” foldout. https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-36151 exists but it’s a regression whereas the “Events” foldout is not. So it's a different issue. Maybe fix Alt/Option + Click for the "Events" foldout as well?
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
- [URP] Crash on GameObject::QueryComponentByType when baking a Reflection Probe in an unsaved/untitled Scene
- No Icons are used for the Entry and Exit States in the Inspector when selected in an Animator Controller
- Crash on PlayerMain(int, char const**) when exiting Standalone Player with a Particle System in the Scene
- No Icon is used for the Runtime Animator Controller Type in a Search Window when assigning an Animator Controller in the Animator Component
- Unity Version Control server textfield’s text overlaps with the dropdown triangle button in the Explore repositories window when an organization with a long name is selected
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.