Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.2.0b4
Issue ID
1158249
Regression
No
Button colors are not correct when you disable then re-enable the button image component.
Button script colours are not correct when you disable then re-enable the button image component.
Steps to reproduce.
- Open Unity 2019.2.0b4
- Create a Canvas in the Hierarchy
- Add a button (Create > Ui > Button)
- In the Inspector change the Button - Normal Color to black.
- In the Inspector disable then enabled the Image component
Notice Issue >> The colour has been reset to white but button script is set to black.
Broken: 2020.1.0a9, 2019.2.0b4, 2019.2.0a11, 2019.2.0a1, 2019.1.2f1
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][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Resolution Note (2020.2.X):
Its kind of by design in terms of the image knows nothing but its own data, and the button is the one controlling the image's color.
OnEnable the image sets its color but the button overrides it, Issue is the button has no knowledge about the image enabled state change.
If there is no real workflow where this is a issue likely wont fix it although (its a bug) as it would involve a change in design principles.