Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.1p1
Issue ID
1004027
Regression
Yes
UI element position is not changed when it's called after SetSizeWithCurrentAnchors()
How to reproduce:
1. Open given Unity project
2. Enter "scene" scene
3. Enter Play Mode
4) Click button labeled "Resize then move"
--Notice that the pink UI element is moved to the same location as the white square, AND resized to the same width.
5) Click button labeled "Reset" to reset the pink UI element to its original size and position.
6) Click button labeled "Move then Resize"
-- Notice that the pink UI element is resized to the same width as the white square, BUT it is not moved to the same location.
Expected result: When button "Move Then Resize" is clicked, pink UI should change the size and position
Actual result: UI size is changed but position remains the same
Regression first introduced in: 2017.3.1p1
Reproducible with: 2018.2.0a1, 2018.1.0b9, 2017.3.1p2
Not reproducible with:2017.3.1p1, 2017.2.2f1, 2017.1.3p1, 5.6.5p2
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
Add comment