Search Issue Tracker
Won't Fix
Won't Fix in 1.6.X
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.
Resolution Note (1.6.X):
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.