W3C home > Mailing lists > Public > www-style@w3.org > May 2016

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

From: Rachel Nabors <rachelnabors@gmail.com>
Date: Mon, 23 May 2016 09:18:11 +0000
Message-ID: <CAPFA0t0ekSBKcdkjVPZZ66ODUHEiQsFpv=xQ+yecjYkARA_q1Q@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>, 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>
Agreed.

On Sun, May 22, 2016 at 2:36 AM Brad Kemper <brad.kemper@gmail.com> wrote:

>
> > 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.
>
-- 
Curator of Web Animation Weekly
Speaking & Workshops
• Apr 05 –06 SmashingConf, San Francisco
• Apr 21 Frontend Masters, online, CSS Animations and Transitions Master
Class
• May 18 –20 Front-Trends Keynote, Warsaw
• Jun 01 CSSconf Nordic, Oslo
Received on Monday, 23 May 2016 09:18:48 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:59 UTC