These are the links to both specs:
In css-align it says:
Computed value: as specified, with <length>s made absolute, and normal computing to zero except on multi-column elements
In css-multicol it says:
Computed value: | as specified, with <length>s made absolute
I'm not sure if this difference is on purpose or not.
I understand that with the current text the computed value of column-gap: normal would be:
0px if it's not a multicol containernormal if it's a multicol container
But now that we're generalizing the properties to apply in other layout models (like grid and flexbox), it seems weird that we have a difference there.
Currently getComputedStyle() is returning normal in all browsers but Edge (where it returns 0px).
I guess we could change this and we have 2 options:
- We can say that it's the computed value for
normal is normal.
- Or that the computed value for
normal is the used value.
Note that if the computed style of normal is normal, then that value won't be animatable. However if it's the used value (0px or 1em in multicol) then it'll be animatable.
[ Edited by @dbaron to fix <production>s that were getting interpreted as HTML tags. ]
These are the links to both specs:
In
css-alignit says:In
css-multicolit says:I'm not sure if this difference is on purpose or not.
I understand that with the current text the computed value of
column-gap: normalwould be:0pxif it's not a multicol containernormalif it's a multicol containerBut now that we're generalizing the properties to apply in other layout models (like grid and flexbox), it seems weird that we have a difference there.
Currently
getComputedStyle()is returningnormalin all browsers but Edge (where it returns0px).I guess we could change this and we have 2 options:
normalisnormal.normalis the used value.Note that if the computed style of
normalisnormal, then that value won't be animatable. However if it's the used value (0pxor1emin multicol) then it'll be animatable.[ Edited by @dbaron to fix <production>s that were getting interpreted as HTML tags. ]