You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an out of flow item is positioned statically in a block/inline formatting context, the spec says to take align-self and justify-self into account.
However, what is expected of align-items and justify-items when set on the originating inline/block parent of the abspos? Normally, align-items and justify-items are the defaults for align-self and justify-self, but in inline layout, align-items and justify-items don't apply in general, and in block layout, align-items doesn't apply to its children. Should abspos elements follow suite and ignore align-items and justify-items if it would have ignored it if it weren't abspos?
I'd assume that we should ignore align-items and justify-items in the same cases for abspos elements such that their static position is as close to what it would have been if not taken out of flow. However, the spec isn't clear on what should happen in this case.
When an out of flow item is positioned statically in a block/inline formatting context, the spec says to take
align-self
andjustify-self
into account.However, what is expected of
align-items
andjustify-items
when set on the originating inline/block parent of the abspos? Normally,align-items
andjustify-items
are the defaults foralign-self
andjustify-self
, but in inline layout,align-items
andjustify-items
don't apply in general, and in block layout,align-items
doesn't apply to its children. Should abspos elements follow suite and ignorealign-items
andjustify-items
if it would have ignored it if it weren't abspos?I'd assume that we should ignore
align-items
andjustify-items
in the same cases for abspos elements such that their static position is as close to what it would have been if not taken out of flow. However, the spec isn't clear on what should happen in this case.CC @bfgeek
The text was updated successfully, but these errors were encountered: