# STEPS TO REPRODUCE: 1. inspect any page with a CSS animation/transition 2. select a node with an active CSS animation/transition in the Elements Tab 3. evaluate: ``` let effect = $0.getAnimations()[0].effect; effect.getKeyframes(); // should not crash effect.target = null; effect.getKeyframes(); // will crash ```
<rdar://problem/60962458>
Created attachment 394761 [details] Patch
Comment on attachment 394761 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=394761&action=review Very nice, thanks for spotting – and fixing – that! > LayoutTests/webanimations/css-animation-effect-target-change-and-get-keyframes-crash.html:1 > +<!DOCTYPE html><!-- webkit-test-runner [ experimental:WebAnimationsCSSIntegrationEnabled=true ] --> We really don't need this but anymore, this is the default and there's No Going Back.
Comment on attachment 394761 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=394761&action=review Thanks for the review Antoine! >> LayoutTests/webanimations/css-animation-effect-target-change-and-get-keyframes-crash.html:1 >> +<!DOCTYPE html><!-- webkit-test-runner [ experimental:WebAnimationsCSSIntegrationEnabled=true ] --> > > We really don't need this but anymore, this is the default and there's No Going Back. I appreciate that, but given that the flag still exists, I think it's safe to still have it. Not to mention, it adds more information about what this test is actually testing.
Committed r259205: <https://trac.webkit.org/changeset/259205> All reviewed patches have been landed. Closing bug and clearing flags on attachment 394761 [details].
*** Bug 210161 has been marked as a duplicate of this bug. ***