Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Motion path spec #66

Closed
shans opened this issue Jul 29, 2015 · 7 comments
Closed

Motion path spec #66

shans opened this issue Jul 29, 2015 · 7 comments
Assignees

Comments

@shans
Copy link

shans commented Jul 29, 2015

https://drafts.fxtf.org/motion-1/

@slightlyoff
Copy link
Member

Are there specific areas of concern that you'd like for us to pay attention to, over and above the issues you linked to?

@dbaron
Copy link
Member

dbaron commented Sep 15, 2015

Some comments:

It seems like it should say more explicitly that it works like the 'transform' property (which I think is the intent). For example, having 'motion-path' should have the effects that 'transform' has like creating a stacking context, being a containing block for absolute and fixed positioned elements, etc.

It also seems like the spec should have some examples with code in them.

@dbaron
Copy link
Member

dbaron commented Sep 15, 2015

Also, the "Applies to" is a little suspicious in terms of being broader than the "transformable elements" set in the CSS Transforms spec.

@slightlyoff
Copy link
Member

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 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?

@plinss
Copy link
Member

plinss commented Jun 13, 2016

These properties have been merged with polar positioning and are currently in the Round Display spec:
https://drafts.csswg.org/css-round-display/#positioning-content

The motion path spec needs to be tombstoned.

@shans
Copy link
Author

shans commented Jun 14, 2016

During the SF face-to-face I thought we had resolved to merge the round display properties into motion-path, not the other way around. Has something changed since?

@plinss
Copy link
Member

plinss commented Jun 14, 2016

Only that the current work seems to be happening in the Round Display spec. I expect it will get moved back to motion-path at some point (or possibly another spec). I don't care where it ends up (or lives now) and am not advocating for any location, I just think it's confusing to have conflicting work in two places, and one of them should just point to the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants