- From: Daniil Sakhapov via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Feb 2023 17:10:08 +0000
- To: public-fxtf-archive@w3.org
danielsakhapov has just created a new issue for https://github.com/w3c/fxtf-drafts: == [motion-1] Make offset-position more specific == Currently [offset-position](https://drafts.fxtf.org/motion/#offset-position-property) says that when it's specified with position it: > Specifies the initial position, with the the containing block as the positioning area and a dimensionless point (zero-sized box) as the object area. But it's not clear if it should calculate the initial position from the computed position (left + top properties, for example) + offset-position. Or it should be containing block (0, 0) + offset-position, ignoring the left, top properties. And taking the note into account: > This is similar to absolute positioning, except that [offset-position](https://drafts.fxtf.org/motion/#propdef-offset-position) does not prevent boxes from impacting the layout of later siblings. I think it needs to be specified how it should interact with other properties like left, top, right, bottom. For example, if I the size of the box is determined by all of that properties, but offset-position is specified, how they should interact? Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/499 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 February 2023 17:10:09 UTC