You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Implicit composition animations fail to run after already running an animation on a property, if that property's modified again. The animation starts to work after another change to that property, and the issue no longer appears until the control is removed and added back to the visual tree.
An example where this occurs is when you have an implicit Offset animation on a control that's in a ScrollViewer. If the control is large enough to be scrollable, changing the Offset from 0 to 100 properly animates the Scrolling. Changing the Offset again, to 0 for example, will not animate the Scrolling. Internally, the Scroll Offset has the correct value, but if there's virtualization on the content, the scrolled to content will not render. Changing the Offset again will fix the issue.
Describe the bug
Implicit composition animations fail to run after already running an animation on a property, if that property's modified again. The animation starts to work after another change to that property, and the issue no longer appears until the control is removed and added back to the visual tree.
An example where this occurs is when you have an implicit Offset animation on a control that's in a ScrollViewer. If the control is large enough to be scrollable, changing the Offset from 0 to 100 properly animates the Scrolling. Changing the Offset again, to 0 for example, will not animate the Scrolling. Internally, the Scroll Offset has the correct value, but if there's virtualization on the content, the scrolled to content will not render. Changing the Offset again will fix the issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Avalonia.Labs.Catalog.2023-03-20.11-13-44.mp4
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: