Search Issue Tracker
By Design
Votes
0
Found in
2021.3.31f1
2022.3.11f1
2023.1.18f1
2023.2.0b12
2023.3.0a11
Issue ID
UUM-54784
Regression
No
"Rect Transform" Component's values are set to 0 when disabling the "Canvas" Component on the same GameObject
How to reproduce:
1. Open the user-attached project “CanvasTest”
2. Open the “SampleScene” scene
3. Enter the Play Mode
4. Observe the Console logs without and with the Canvas Component
Expected result: Both logs return the “293”
Actual result: The Console output without Canvas is “0” and “293” with the Canvas Component
Reproducible with: 2021.3.31f1, 2022.3.11f1, 2023.1.18f1, 2023.2.0b12, 2023.3.0a11
Reproducible on: Windows 11 Pro
Note: The user has mentioned this issue didn’t happen in the 2020.3 stream but it was reproducible for me. However, the returned number was different
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note:
Positions are not guaranteed if the Canvas component is disabled. They may have been kept at some point but if there's no rendering there's no way to rely on layout.