- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Sat, 21 May 2016 17:31:28 -0700
- To: Jihye Hong <jh.hong@lge.com>
- Cc: Shane Stephens <shans@google.com>, fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>, florian@rivoal.net, eoconnor@apple.com, Dean Jackson <dino@apple.com>, Song Hyojin <hyojin22.song@lge.com>
> On May 18, 2016, at 2:49 AM, Jihye Hong <jh.hong@lge.com> wrote: > > We need 'motion-origin'(which will be changed to 'offset-anchor') separately from 'transform-origin'. > 'motion-origin' is required not only for rotating the element. It's also for setting the origin point in the element's > content area which is placed at different positions along the motion path. I know we were conflating the two needs in the meeting, but I think setting the origin point of the rotation needs to be separate from setting the reference point (offset-origin) for aligning to the offset-position in the containing block. 'offset-origin:auto’ would mean that 'offset-position:100% 100%’ puts the reference point in the lower right corner (a la background-position), but this should not affect where the origin of the rotation should be, which might need to be somewhere else.
Received on Sunday, 22 May 2016 00:31:59 UTC