- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 05 Nov 2016 01:15:04 +0000
- To: public-fxtf-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion] <angle> notation should be defined as bearing angles == The description for `<angle>` values right now is very confusingly written. It should just reference bearing angles, like gradients do. Current prose: > <angle> > The path is a line segment that starts from the position of the element and proceeds in the direction defined by the specified `<angle>` from the y axis. For `<angle>`, the initial value none is interpreted as 0deg, the element can be positioned along the y axis. If the `<angle>` value increases in the positive direction, the element moves clockwise. Proposed prose: > <angle> > The path is a line segment that starts from the position of the element and proceeds in the direction defined by the specified `<angle>`. As with [CSS gradients](https://www.w3.org/TR/css3-images/#gradients), `<angle>` values are interpreted as bearing angles, with `0deg` pointing up and positive angles representing clockwise rotation. Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/63 using your GitHub account
Received on Saturday, 5 November 2016 01:15:10 UTC