-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fixed incorrect timed keyframe expression #3921
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed incorrect timed keyframe expression #3921
Conversation
|
Thanks Sergio0694 for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
|
Hello @RosarioPulella! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
8e46c5d to
1c5269a
Compare
1c5269a to
09cb085
Compare
09cb085 to
b57da01
Compare
|
@Sergio0694 @JustinXinLiu seems like something serious enough we may want to patch? Thoughts? |
|
@Sergio0694 was this exposed in one of the samples? Is there a way we can visually validate the fix for comparison? |
Yes, if it was possible to do a hotfix release before 7.1 I'd say this should probably be included. Granted, it's a pretty niche scenario since you need to:
Which I guess also explain why we didn't notice it before.
It wasn't, as these APIs are not available from XAML (it only supports normalized keyframes, which are the default).
It's not much about a visual difference, it's more that without this fix the animation wasn't playing at all 😅 |
|
Thanks @Sergio0694 let's merge this in to get the fix so things work, and think about general animation testbed for checking things 'in-flight' for the future. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The
TimedKeyFrameAPIs are using an incorrect expression, resulting in the animation not playing.What is the new behavior?
Fixed the expression to calculate the normalized timestamp of timed keyframes, so they work fine now 😄
PR Checklist
Please check if your PR fulfills the following requirements:
Pull Request has been submitted to the documentation repository instructions. Link:Sample in sample app has been added / updated (for bug fixes / features)Icon has been created (if new sample) following the Thumbnail Style Guide and templates