Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.2.0b5
2023.1.0a6
2023.2.0a1
Issue ID
UUM-12278
Regression
No
"Some values are driven by Canvas" message isn't shown when Prefab is selected in the Project Browser
How to reproduce:
1. Open the user’s attached “UnityBug_RectTransformPrefabVariant” project
2. Select the “Canvas” Prefab in the Project Browser
3. Observe the “Rect Transform” Component in the Inspector
Expected result: Component is greyed out with the “Some values are driven by Canvas” message in the Inspector
Actual result: Component isn’t greyed out, leading to modification allowance to the serialized fields under the Component
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b5, 2023.1.0a6
Reproduced on: macOS 12.3 (Intel)
Note:
Prefab instances in the Hierarchy are working as expected
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
- Unity Hub Module icons wrap poorly when they occupy two rows
- "Add new query block" (+) button has no highlight when navigated with the keyboard
- WebGPU errors when CoreCopy shader is used to copy an MSAA texture
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
Resolution Note:
In the attached project, the prefab does not know where the object will be landed in the hierarchy. If it is put in the root level, its values are driven by Canvas. However, if it is put in the child level, the values are directly coming from the prefab. Therefore, it might or might not be driven by Canvas depending on how it will land on the hierarchy. Not showing the "Some values are driven by Canvas" message is appropriate here until it lands on the hierarchy. In addition, this behavior has been consistent since 2019.1. So the overall behavior is consistent, expected and documented (https://docs.unity3d.com/Packages/com.unity.ugui@1.0/manual/UIBasicLayout.html).
Resolution Note (2023.2.X):
In the attached project, the prefab does not know where the object will be landed in the hierarchy. If it is put in the root level, its values are driven by Canvas. However, if it is put in the child level, the values are directly coming from the prefab. Therefore, it might or might not be driven by Canvas depending on how it will land on the hierarchy. Not showing the "Some values are driven by Canvas" message is appropriate here until it lands on the hierarchy. In addition, this behavior has been consistent since 2019.1. So the overall behavior is consistent, expected and documented (https://docs.unity3d.com/Packages/com.unity.ugui@1.0/manual/UIBasicLayout.html).