Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.7f1
2023.2.0b3
Issue ID
UUM-44496
Regression
No
Color values in the “Button” Component are not reverted to default when pressing the “Reset” Component button in the Play Mode
How to reproduce:
1. Open the user’s attached “MedievalMayhem.zip” project
2. Enter Play Mode
3. In the Hierarchy window, expand “Pause Menu Canvas” > “Pause Menu UI” and select “Menu” GameObject
4. In the Inspector window, change “Normal Color” to any color
5. Press on the three dots of the “Button” Component and press “Reset”
6. Observe the “Normal Color”
Expected result: “Normal Color” is reset
Actual result: “Normal Color” is not reset
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3
Reproduced on: macOS 13.4.1 (Intel)
Notes:
-reproducible with other colors as well
-not reproducible without entering Play Mode
Workaround: disabling and re-enabling the "Button" component (user’s info)
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.
Resolution Note (2023.2.X):
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.