Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.2.X, 2018.3.X
Votes
0
Found in
2018.2.0x
2018.2.0a4
Issue ID
1086672
Regression
Yes
Sprite Editor border "T" and "B" fields assign their values to the wrong borders
How to reproduce:
1. Open the attached project (SpriteBorder.zip)
2. Open the Sprite Editor Window
3. Inspect the "Map__16_Checker" asset in the Sprite Editor
4. Notice how the value of 200 is assigned to the "T" field rather than "B"
Expected result: The border with the value of 200 is labeled as "B" and not "T"
Actual result: The border with the value of 200 is labeled as "T" and not "B"
Reproducible with: 2018.2.0a4, 2018.2.11f1, 2018.3.0b4, 2019.1.0a2
Not reproducible with: 2017.4.0f1, 2017.4.12f1, 2018.1.9f2, 2018.2.0a3
Notes: It doesn't seem like the fields are simply mislabeled, as the value of 200 jumps fields between versions
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
- The Frame value field does not update when using the increment/decrement arrows in the Frame Debugger if the value has been manually inputted
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
Resolution Note (fix version 2019.1):
ba592c1f180d