Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.0f1c1
2022.1
2022.2
Issue ID
1383554
Regression
No
RectTransfom Child's position changes automatically when Parent's width is relatively large and Child is anchored left or right
Changing Parent object (under Canvas) RectTransform's width will make its Child's Anchored position slightly changed due to precision issue
Reproduction steps:
1. Create any object under Canvas
2. Set the object's RectTransform's width to 1000
3. Add a Child object under the previously created Parent (which is a child of Canvas)
4. Set the down most Child object Anchor Preset to left or right and its position X to 14.4
5. Increase the Parent's width gradually, and observe the Child's position X
Expected result: Child's object relative position X does not change
Actual result: When the Parent object width increases to above 1050, Child's position X is changed to 14.40002 automatically
Reproducible with: 2019.4.36f1, 2020.3.30f1, 2021.2.14f1, 2022.1.0b10, 2022.2.0a6
Notes:
- Down most Child object Anchor Preset must be set to left or right
- It is not possible to set the Child's position back to 14.4 again without recreating the object
- Does not reproduce with the position Y or by changing parent's height
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
After investigation we have deemed this a low priority issue that wont be fixed in the near future. There is float imprecision issues. If you feel this is a wrong assessment please reach out again.