Search Issue Tracker
Active
Votes
1
Found in
2022.3.57f1
6000.0.36f1
6000.1.0b4
6000.2.0a2
Issue ID
UUM-96681
Regression
No
UI Toolkit Transition Animation is ignored when background-size property has a starting value of 0
Reproduction steps:
1. Open the attached “AnimationBug.zip” project
2. Open the “SampleScene”
3. Enter the Play mode
4. Hover the mouse over the white rectangle
5. Observe the animation
Expected result: The rectangle transitions to pink with an transition animation
Actual result: The rectangle instantly turns pink
Reproducible with: 2022.3.57f1, 6000.0.36f1, 6000.1.0b4, 6000.2.0a2
Reproducible on: macOS 15.2 (Intel) (User reported), Windows 11
Not reproducible on: No other environment tested
Workaround: Open the test.uxml in UI Builder and select the .test selector. Expand the Background property and edit the Size Width property to any value other than 0. Save the file, and then edit the property back to 0 and save again. The animation transition is then visible when in Play mode even when the value is 0.
Notes:
- The issue reappears every time the Editor is reopened
- Also reproduces in Windows and WebGL builds
Comments (1)
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
- "ShaderGraph" misses a space in the "Project Settings" section
- UI Builder inspector’s checkbox fields can be activated when clicking anywhere in the value field
- Unity icon is poorly visible in the "Build Profiles" window when "Dark" editor theme is selected
- UI Toolkit Transition Animation is ignored when background-size property has a starting value of 0
- Error "Assertion failed on expression: 'i->previewArtifactID == found->second.previewArtifactID'" is present when creating Render Texture
ANTONBORODA
Feb 03, 2025 12:38
Issue description says that the issue does not reproduce in player, which is incorrect!
The issue does reproduce in player (on WebGL, at least) if the project is built with the issue being active in the editor.
It does not reproduce sometimes, however clearing Library folder and building after the initial reimport without any workaround tricks will make the issue appear in player (WebGL).