181116 2017-12-22 00:15:13 -0800 [Web Animations] Create new promises rather than just calling .clear() 2023-02-17 02:19:50 -0800 1 1 1 Unclassified WebKit Animations Safari Technology Preview Unspecified Unspecified RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=180402 InRadar P2 Normal --- 1 graouts graouts bennyfagan13 dino graouts webkit-bug-importer oldest_to_newest 1384414 0 graouts 2017-12-22 00:15:13 -0800 The patch for https://bugs.webkit.org/show_bug.cgi?id=180402 makes the test at http/wpt/web-animations/interfaces/Animation/finished.html crash due to an assertion in the Promise code. It turns out we're using .clear() on an existing promise rather than creating a whole new promise as the spec mandates, we need to address this as soon as the patch for https://bugs.webkit.org/show_bug.cgi?id=180402 lands. 1384415 1 webkit-bug-importer 2017-12-22 00:15:44 -0800 <rdar://problem/36192416> 1384416 2 webkit-bug-importer 2017-12-22 00:15:44 -0800 <rdar://problem/36192415> 1512566 3 bennyfagan13 2019-03-05 01:35:15 -0800 I have learned how to move animations from templates to JavaScript, isolating introduction from conduct. I never depend on dom procedures, for example, composing css properties and checking classes onto components to control playbacks. What's more, not normal for unadulterated, decisive CSS, JavaScript additionally lets us powerfully set values for durations. https://www.pbase.com/milenaglen/profile https://axlethemes.com/support-forum/users/dennismedina/ https://ghc.haskell.org/trac/summer-of-code/ticket/2593 1934507 4 graouts 2023-02-17 02:19:50 -0800 This has been done for quite some time.