Re: [fxtf-drafts] [css-motion] handling of both offset-position and offset-anchor being auto should be defined clearly

Thanks fantasai.


One detail I hadn't noticed earlier is that the transform-origin 
doesn't always default to center:

https://drafts.csswg.org/css-transforms/#transform-origin-property
"The initial used value for SVG elements without associated CSS layout
 box is 0 0."

Chrome shipped using transform-origin before offset-anchor existed, 
and changing to center instead of the transform-origin 0 0  makes some
 existing motion path demos change behavior.



Would the following be reasonable?

The initial value of offset-anchor should be 'auto', with text that 
'auto' means that **transform-origin** is used as the anchor position,
 unless the offset-position is a \<position\> and offset-path is 
'none': in that case offset-position is used as the offset-anchor.


-- 
GitHub Notification of comment by ewilligers
Please view or discuss this issue at 
https://github.com/w3c/fxtf-drafts/issues/46#issuecomment-258755630 
using your GitHub account

Received on Monday, 7 November 2016 06:18:01 UTC