A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/web-platform-tests/wpt/issues/35420 below:

Clarification on static position of absolutely positioned children of flex containers · Issue #35420 · web-platform-tests/wpt · GitHub

@dholbert @davidsgrogan

I am trying to understand the expectations for the static position of an absolutely positioned child of a flex container. As an example css-flexbox/abspos/flex-abspos-staticpos-align-content-005.html expects containers whose align-content is either normal or stretch and whose available space is negative to place their abspos child differently than when align-content is flex-start (lines 57, 67, and 75 respectively).

Reading the spec for align-content, it seems pretty clear that in the case of the .small containers, the align-content: normal and align-content: stretch are to behave as align-content: flex-start. What I don't understand is why then the expected position is different for the divs at lines 57 and 67 and the div at line 75 in the above test.

Could you help me to understand this expectation and what other calculation for position I might be missing? Does it have to do with align-self being used in the positioning for some values of align-content?


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3