Re: [spec-reviews] Motion path spec (#66)

A few thoughts:

 * There don't appear to be any meaningful examples in the spec. Had to go dig them out of the Chromium repo (here)[https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/LayoutTests/css3/motion-path/&q=motion-offset&sq=package:chromium&type=cs]. This is a pretty big issue.
 * The `transform-box` which is the root of the transformation [is spec'd](https://drafts.csswg.org/css-transforms-1/#transform-box) but appears to be a new property with uncommon semantics. Why was this chosen instead of a more locally-familiar coordinate system?
 * It seems the interactions with layout aren't called out well. I.e., these things create stacking contexts, become containing blocks, etc., no?

---
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/66#issuecomment-140510455