Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4.8f1
2021.1
Issue ID
1289624
Regression
No
UI component's reference gets copied when copying it to another GameObject
How to reproduce:
1. Create a new project
2. Create 2 buttons in the scene
3. Remove Button component in the second Button
4. Copy Button Component from the first Button
5. Paste component as new to the second Button
6. Change the color of the second Button
Expected result: Color of the second Button changes
Actual result: Color of the first Button changes
Reproducible with: 2018.4.29f1, 2019.4.14f1, 2020.1.14f1, 2020.2.0b11, 2021.1.0a6
Notes:
- Reproduces on components that have several color fields (Button, Dropdown, Scrollbar), not with Image component
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
- 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
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
A graphic needs to be specified for the component to work. It gets told which Graphic is is controlling. There is no expectation that a Button component is on the Graphic component it could be on another GO.