Re: [round-display] [motion-path] Orientation of elements due to merging polar positioning and motion path

> On May 17, 2016, at 8:11 PM, Shane Stephens <shans@google.com> wrote:
> 
> You need to specify an order that everything gets assembled into a transformation matrix.
> 
> Currently we have:
> 
> apply motion (= motion translation, motion rotation)
> apply translate
> apply rotate
> apply scale
> apply transform

I don't think my syntax suggestion would change that much, other than to make it a bit simpler. It would be:

apply motion (= motion translation)
apply translate
apply rotate (including calculated rotation based on earlier motion translation)
apply scale
apply transform

You might get somewhat odd results by combining motion translation with translate(), I guess, but the solution is for authors to not do that, or to do it with eyes wide open. It would be different from what is expected in current motion-path spec, but not necessarily bad.