-
Notifications
You must be signed in to change notification settings - Fork 56
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
Comments
Are there specific areas of concern that you'd like for us to pay attention to, over and above the issues you linked to? |
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. |
Also, the "Applies to" is a little suspicious in terms of being broader than the "transformable elements" set in the CSS Transforms spec. |
A few thoughts:
|
These properties have been merged with polar positioning and are currently in the Round Display spec: The motion path spec needs to be tombstoned. |
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? |
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. |
https://drafts.fxtf.org/motion-1/
The text was updated successfully, but these errors were encountered: