- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jul 2020 20:53:32 +0000
- To: public-css-archive@w3.org
bfgeek has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-position-3] Auto margin resolution isn't symmetrical. == https://drafts.csswg.org/css-position-3/#abspos-margins > Otherwise, the remaining space is calculated as the size of its inset-modified containing block in the relevant axis minus the box’s used size in the relevant axis, and this remaining space is divided among any auto margins in the relevant axis. However, if the remaining space is negative and both margins are auto, the start margin resolves to zero and the end margin receives the remaining space. There is a sutle different between the horizontal and vertical (or inline, and block? - needs research) algorithms: https://drafts.csswg.org/css-position-3/#abs-non-replaced-width https://drafts.csswg.org/css-position-3/#abs-non-replaced-height See this testcase: https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=8318 In the vertical (or block, but which block?) direction negative auto margins get distributed evenly between the top and bottom, where-as horizontal (or inline) the inline-start margin is zero. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5374 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 July 2020 20:53:34 UTC