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
In most cases it is preferable to have the default replace behaviour that we have currently for (web) animations (i.e. "I want to animate from opacity 0 to 1 regardless of what the current value is").
One special case that I ran into is where an element already has a transform defined. We currently provide no nice way to keep that transform in effect, while the user is at the moment simply saying to the system "I want to animate the position of the element".
We probably have to read out the current value and possibly combine it into the keyframes (?) (or automatically select a different composite option in case we detect a pre-existing value that we need to keep).
I'll make a branch with a demo that showcases the issue soon.
The text was updated successfully, but these errors were encountered:
nickschot
changed the title
Composite style handling
Composite style handling (color, transform etc.)
Aug 19, 2022
In most cases it is preferable to have the default
replace
behaviour that we have currently for (web) animations (i.e. "I want to animate from opacity 0 to 1 regardless of what the current value is").One special case that I ran into is where an element already has a transform defined. We currently provide no nice way to keep that transform in effect, while the user is at the moment simply saying to the system "I want to animate the position of the element".
We probably have to read out the current value and possibly combine it into the keyframes (?) (or automatically select a different composite option in case we detect a pre-existing value that we need to keep).
I'll make a branch with a demo that showcases the issue soon.
The text was updated successfully, but these errors were encountered: