- From: Boris Chiou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 May 2023 23:38:12 +0000
- To: public-fxtf-archive@w3.org
BorisChiou has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] The syntax of "offset" shorthand is out-of-date == After the updating of [`offset-position`](https://drafts.fxtf.org/motion-1/#offset-position-property) and [`offset-path`](https://drafts.fxtf.org/motion-1/#offset-path-property), we have the offset transform (and create stacking context) only when `offset-path` is not `none`. `offset-position` is used only when `offset-path` functions don't specify the offset starting position. So the [current syntax of `offset` shorthand](https://drafts.fxtf.org/motion-1/#offset-shorthand) is out-of-date. > [ <'offset-position'>? [ <'offset-path'> [ <'offset-distance'> || <'offset-rotate'> ]? ]? ]! [ / <'offset-anchor'> ]? The exclamation point (`!`) doesn't make sense now. It's not necessary to have `offset-position` if we don't specify `offset-path`. Perhaps we should always specify `offset-path`, and move `offset-position` together with `offset-anchor` or other places? Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/515 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 May 2023 23:38:14 UTC