Search Issue Tracker
Fixed
Fixed in 2020.3.47f1, 2021.3.22f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a7
Votes
0
Found in
2020.3.45f1
2021.3.18f1
2022.2.7f1
2023.1.0b4
2023.2.0a3
Issue ID
UUM-27611
Regression
No
The Button is interactable when instantiated into a non-interactable Canvas Group
How to reproduce:
# Open the attached project "BugNavigation.7z"
# Enter Play Mode
Expected results: The "I should be inactive" Button is inactive
Actual results: The "I should be inactive" Button is active
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.7f1, 2023.1.0b4, 2023.2.0a3
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment