[css-grid-3][masonry] Static positions of out-of-flow items in fill-reverse

[celestepan]

In the case we are using fill-reverse on a grid-lanes container (ie either grid-lanes-direction: row fill-reverse or grid-lanes-direction: column fill-reverse), do we expect the static positions of the out-of-flow items to be reversed along the stacking axis as well?

For example, for column fill-reverse, should the static position of the OOF item be at the end of the container, where the in-flow items are starting:

or should the static position of the OOF item be at the start of the container:

I think it makes the most sense to have the static position of the out-of-flow items calibrate to wherever the rest of the in-flow items are starting, since the static position of an out-of-flow item represents where the item would be placed if it were in-flow.

[celestepan]

cc @mhochk @alisonmaher @KurtCattiSchmidt @yanlingwang23

[alisonmaher]

One additional thing to note is the relevant spec text at: https://drafts.csswg.org/css-grid-2/#static-position

The static position [CSS2] of an absolutely-positioned child of a grid container is determined as if it were the sole grid item in a grid area whose edges coincide with the content edges of the grid container.

Per this text, OOF items are not currently impacted by content alignment, but it isn't clear what should happen with reversals (as I think the question could apply to track-reverse, as well).

I tend to agree that it would likely make sense for OOFs to honor reversals in these cases.