- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Mar 2023 19:57:11 +0000
- To: public-fxtf-archive@w3.org
Ah you know what, iirc the Motion spec *used* to be defined on top of abspos, rather than being a transform; offset-position (and -anchor) were never properly rewritten after the change. Okay, so summary of changes in 2823e66: * Clarified that offset-position only applies to offset paths that don't predefine their initial position (that is, only `ray()`). * Removed any mention of 'position' from the values, since it's irrelevant. * Removed the text about non-auto causing a stacking context/containing block; that behavior is caused by a non-none 'offset-path' itself, not by 'offset-position'. While doing this I realized that the specified behavior of `auto` (particularly when combined with a non-auto `offset-anchor` is nonsensical; I'll raise a separate issue for this. Does this look good to y'all? -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/499#issuecomment-1454058058 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 March 2023 19:57:13 UTC