Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3.0a11
2019.3.8f1
2020.1
2020.2
Issue ID
1234614
Regression
Yes
Transform.position is different in Start and Update methods on WebGL builds when Canvas Scaler is set to Scale with Screen Size
How to reproduce:
1. Open the project "case_1234614-WebGL_transform.position"
2. Open the scene "SampleScene"
3. Make a WebGL build and run it
4. Observe the results in the Console window
Expected results: the values of the Transform.position of the GameObject "Image" are the same in the Start() and in the Update() methods
Actual results: the values of the Transform.position of the GameObject "Image" are different in the Start() and in the Update() methods
Reproducible with: 2019.3.0a11, 2019.3.8f1, 2020.1.0b5, 2020.2.0a7
Not reproducible with: 2018.4.21f1, 2019.3.0a10
Could not test with: 2017.4.39f1 due to errors
Tested on: Chrome (81.0.4044.92), Firefox (75.0), Microsoft Edge (44.18362.449.0)
Notes:
1. It is only reproducible when the Canvas Scaler is set to Scale with Screen Size
2. It is not reproducible with the Transform.localPosition
3. The values of Transform.position changes after the first execution of the Update method
4. It is reproducible only on WebGL builds
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
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
- m_Modifications block serializes incorrectly when replacing source prefabs
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a14