Issue with "rotate/rotation" property inside of motionPath?

[green_machine]

I often use non-position properties in a motion path, but found a potential bug with the "rotate" property inside of an array of motionPath values. In my CodePen, you can see that using "rotation" works just fine, but when using "rotate", nothing happens. The only different between the two lines other than the selector is the "rotate/rotation" property swapped out.

 

Am I missing something obvious here? I switched to using "rotate" over "rotation" in 3.0 to stay consistent with how I'd write it in CSS, so was curious if I encountered a bug here or if I am messing something up.

See the Pen 8c674b01dc6276a7cc2a7662836e76d2 by dsenneff (@dsenneff) on CodePen

[GreenSock]

Yeah, that's because the official GSAP property is "rotation", but when you directly animate things via CSSPlugin it'll accept some aliases too like "rotate" (which internally we just map to "rotation"). MotionPathPlugin wasn't able to do that mapping. I'll update the next version of MotionPathPlugin to look for those aliases too - here's a preview: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/MotionPathPlugin.min.js

 

Better? 

 

By the way, thanks so much for the reduced test case! Super helpful. 

[green_machine]

Ah, I gotcha. I misread then; I thought in 3.0 that you meant that you could now use "rotate" across the board in GSAP, which I prefer since it matches CSS now and not AS (and it's also fewer characters). If it means you had to add logic now to convert "rotate" to "rotation" everywhere behind the scenes then no need, I can just go back to using "rotation" instead and keep the library leaner.