- From: pyoor via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Oct 2020 15:58:44 +0000
- To: public-fxtf-archive@w3.org
pyoor has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] Incorrect type definition link in <size> == The `ray()` definition syntax links to the `<size>` definition in css-images-3, however; it appears that ray only accepts a limited number of these arguments: `[ closest-side | closest-corner | farthest-side | farthest-corner | sides ]` https://github.com/w3c/fxtf-drafts/blob/cb4c0bb766ccc4a6670c240107c934865389089c/motion-1/Overview.bs#L126 I'm not sure what the usual process is for name conflicts among types. Should the `<size>` definition be replaced with a group defintion containing: `[ closest-side | closest-corner | farthest-side | farthest-corner | sides ]` Or are these types of naming conflicts allowed? And if so, the link in the `ray()` function should be changed to https://drafts.fxtf.org/motion-1/#valdef-offsetpath-size Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/411 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 October 2020 15:58:46 UTC