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
{{ message }}
Repository navigation
[css-flexbox][css-align][css-grid] Incompatible spec for align-self computed value when 'auto' #644
It seems that last month it was agreed than 'auto' values on align-self and justify-self compute to itself from now on, based on #440 .
I have to say that it's surprising that, after some many discussions, we've ended up with this approach. But anyway, this is in conflict with what the current draft of Flexible Box states for the align-self property:
On absolutely positioned elements, a value of auto computes to itself. On all other elements, a value of auto for align-self computes to the value of align-items on the element’s parent, or stretch if the element has no parent.
I think we need to match both specs, otherwise the implementation of the CSS Alignment specification is going to be really difficult.
I think the key limitations leading to this were that a) absolutely-positioned boxes need auto to compute to itself whereas all other boxes take the value from the parent's align-items, making the computation depend on position, and b) Gecko folks don't like cross-property computed value dependencies. Since neither animation nor inheritance provide significant use cases here that we need to consider, we went with the route that yields less accurate computed values in favor of ease-of-implementation.
On absolutely positioned elements, a value of auto computes to itself. On all other elements, a value of auto for align-self computes to the value of align-items on the element’s parent, or stretch if the element has no parent.
Activity
fantasai commentedon Nov 25, 2016
I think the key limitations leading to this were that a) absolutely-positioned boxes need auto to compute to itself whereas all other boxes take the value from the parent's align-items, making the computation depend on
position, and b) Gecko folks don't like cross-property computed value dependencies. Since neither animation nor inheritance provide significant use cases here that we need to consider, we went with the route that yields less accurate computed values in favor of ease-of-implementation.mrego commentedon Feb 22, 2017
Hi @fantasai it seems that as part of this change, you forget to update the text on the spec:
[css-flexbox] Remove paragraph wrt computed values per #644 (WG resol…
fantasai commentedon Feb 23, 2017
Thanks, @mrego :) Should be fixed now.
[css-flexbox] Remove paragraph wrt computed values per...