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] <angle> notation should be defined as bearing angles #63

Closed
fantasai opened this issue Nov 5, 2016 · 0 comments
Closed

[motion] <angle> notation should be defined as bearing angles #63

fantasai opened this issue Nov 5, 2016 · 0 comments
Labels

Comments

@fantasai
Copy link
Contributor

fantasai commented Nov 5, 2016

The description for <angle> values right now is very confusingly written. It should just reference bearing angles, like gradients do.

Current prose:

The path is a line segment that starts from the position of the element and proceeds in the direction defined by the specified `` from the y axis. For ``, the initial value none is interpreted as 0deg, the element can be positioned along the y axis. If the `` value increases in the positive direction, the element moves clockwise.

Proposed prose:

The path is a line segment that starts from the position of the element and proceeds in the direction defined by the specified ``. As with [CSS gradients](https://www.w3.org/TR/css3-images/#gradients), `` values are interpreted as bearing angles, with `0deg` pointing up and positive angles representing clockwise rotation.
ewilligers pushed a commit to ewilligers/fxtf-drafts that referenced this issue Nov 14, 2016
The description is now clearer, using text suggested by fantasai.

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

No branches or pull requests

1 participant