Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.2.0b2
2020.3
2020.3.4f1
2021.1.0a1
Issue ID
1331198
Regression
Yes
The value field is not aligned properly when a Range component is added to a Label
How to reproduce:
1. Open the user's attached "1331198.zip" project
2. Open the "SampleScene" Scene
3. In the Hierarchy select the "TestGO" GameObject
4. Observe the inspector
Expected results: The variable, which has the Range slider, has the value field's edge aligned with other value fields in the Inspector
Actual results: The variable, which has the Range slider, has the value field's edge extends more than other value fields in the Inspector
Reproducible with: 2020.2.0b2, 2020.3.4f1, 2021.1.0a1
Not reproducible with: 2019.4.23f1, 2020.2.0b1, 2021.1.0a2, 2021.1.5f1, 2021.2.0a14
Can't test with: 2018.4.33f1 (downgraded script throws errors)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.2):
Fixed in 2021.1.0a2