RESOLVED DUPLICATE of bug 257861 258134
REGRESSION (iOS 17 beta): Playing animation in reverse not working in keyframes are same as previous animation
https://bugs.webkit.org/show_bug.cgi?id=258134
Summary REGRESSION (iOS 17 beta): Playing animation in reverse not working in keyfram...
Liam DeBeasi
Reported 2023-06-15 07:50:20 PDT
Created attachment 466701 [details] Code reproduction Playing an animation in reverse does not work in iOS 17 if the reversed keyframes are the same as an existing animation applied to the same element. Steps to reproduce: 1. Open code reproduction on an iOS 17 device. 2. Tap "Run Accelerated Test". Observe that the element translates from 0px to 100px, jumps back to 0px, and then jumps to 100px. Expected Behavior: I expect that the square will smoothly translate from 0px to 100px, jump back to 0px, and then smoothly translate to 100px. Actual Behavior: The square jumps to 100px after jumping back to 0px. Other Information: - This looks similar to https://bugs.webkit.org/show_bug.cgi?id=257861. I wasn't sure if they were the same, so feel free to merge the two threads if they are. - This works as expected on iOS 16. - This works as expected on Chrome and Firefox for macOS. - This seems to only impact accelerated animations. Tapping "Run Non-Accelerated Test" does not reproduce the issue using margin-left. - Running the second set of keyframes from 0px to 100px without using "direction: 'reverse'" yields the expected behavior. You can try this using the "Run Accelerated Test Without Reversing" button.
Attachments
Code reproduction (2.14 KB, text/html)
2023-06-15 07:50 PDT, Liam DeBeasi
no flags
Radar WebKit Bug Importer
Comment 1 2023-06-15 14:22:03 PDT
zalan
Comment 2 2023-06-23 10:33:02 PDT
Thank you for filing this bug. Great test case!
zalan
Comment 3 2023-06-23 10:34:48 PDT
>This looks similar to https://bugs.webkit.org/show_bug.cgi?id=257861. I wasn't sure if they were the same, so feel free to merge the two threads if they are. Yup, you are correct. This is a dupe of bug 257861. *** This bug has been marked as a duplicate of bug 257861 ***
Note You need to log in before you can comment on or make changes to this bug.