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-align][css-multicol] Make "column-gap: normal" to be 1em in multi-column per spec #2145
The Working Group just discussed Make "column-gap: normal" to be 1em in multi-column per spec, and agreed to the following resolutions:
RESOLVED: remove the UI defined bit and go with 1em for computing normal in multi-col
The full IRC log of that discussion
<dael> Topic: Make "column-gap: normal" to be 1em in multi-column per spec
<dael> AmeliaBR: In the multi-col spec there's a suggested value of 1em
<dael> AmeliaBR: Everyone is doing 1em so we suggest it's mandatory.
<AmeliaBR> s/AmeliaBR/rachelandrew /
<dael> florian: And this interop includes print. Let's go for it.
<dael> github: https://github.com//issues/2145#issuecomment-377445142
<fantasai> s/AmeliaBR/rachelandrew/
<dael> astearns: proposed is remove the UI defined bit and go with 1em for computing normal in multi-col
<dael> RESOLVED: remove the UI defined bit and go with 1em for computing normal in multi-col
Activity
rachelandrew commentedon Dec 29, 2017
Do we know what non-web browser UAs are doing here? I imagine they may be using something different.
frivoal commentedon Jan 3, 2018
At least Vivliostyle, Prince, and Pdfreactor use
1emas well. I do not have an Antenna House install to test, but i'd be surprised if it differed.frivoal commentedon Mar 29, 2018
@MurakamiShinyu Do you know what the behavior of AH formatter is for this? Is column-gap normal 1em, or some other value?
MurakamiShinyu commentedon Mar 30, 2018
AH formatter uses 1em as well.
frivoal commentedon Mar 30, 2018
In that case, I think we should just resolve that it's 1em, and remove the "UA defined" bit, as that doesn't seem to help anyone.
rachelandrew commentedon Mar 30, 2018
I agree, it seems that there is interop on this, so there seems no sense in leaving room for ambiguity.
css-meeting-bot commentedon Apr 4, 2018
The Working Group just discussed
Make "column-gap: normal" to be 1em in multi-column per spec, and agreed to the following resolutions:RESOLVED: remove the UI defined bit and go with 1em for computing normal in multi-colThe full IRC log of that discussion
<dael> Topic: Make "column-gap: normal" to be 1em in multi-column per spec<dael> AmeliaBR: In the multi-col spec there's a suggested value of 1em
<dael> AmeliaBR: Everyone is doing 1em so we suggest it's mandatory.
<AmeliaBR> s/AmeliaBR/rachelandrew /
<dael> florian: And this interop includes print. Let's go for it.
<dael> github: https://github.com//issues/2145#issuecomment-377445142
<fantasai> s/AmeliaBR/rachelandrew/
<dael> astearns: proposed is remove the UI defined bit and go with 1em for computing normal in multi-col
<dael> RESOLVED: remove the UI defined bit and go with 1em for computing normal in multi-col
[css-align-3] Multi-col 'normal' gaps are always 1em per total interop.
rachelandrew commentedon Apr 5, 2018
failed to reference the issue, but commit is here for multicol bf38268
[css-multicol] column-gap normal is 1em per spec now
[css-align-3] Multi-col 'normal' gaps are always 1em per total interop.