Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
1
Found in
2018.4.0f1
2019.2.0a1
2019.3.0a1
2019.3.0b1
2020.1.0a1
Issue ID
1183703
Regression
No
UnityEngine.MinAttribute is not restricting the value of a variable when using the Inspector window
To reproduce:
1. Open attached project ("case_1183703.zip")
2. Open "Test" Game Object from Hierarchy
3. In the Inspector window try to reduce "Min" variable value below 1
Expected result: It's not possible to reduce it below 1
Actual result: It's possible to reduce it below 1
Reproducible in: 2018.4.9f1, 2019.2.6f1, 2019.3.0b3, 2020.1.0a4
Could not test in: 2017.4.32f1 (MinAttribute not introduced)
Comments (1)
-
rasul-is-about-to-fun
May 19, 2020 08:24
what a shame guys.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.1):
Fixed in: 2019.3.0b6, 2020.1.0a7