Repository navigation
[css-multicol] pseudo-algorithm refers to "track size", terminology not already used in the spec #3649
Description
In a workshop with a group of authors it was noted that the pseudo-algorithm (https://drafts.csswg.org/css-multicol-1/#pseudo-algorithm) refers to track size. However this is the first time that tracks are mentioned in the multicol spec.
This was added based on this resolution, to unify grid and flexbox. However it seems that we need to define tracks somewhere as the sudden appearance of this stood out to authors.
Metadata
Metadata
Assignees
Labels
No labels
Activity
frivoal commentedon Mar 1, 2019
Referring to columns would seem more appropriate there. Unless the meaning is intended to be different somehow, in which case we really need a definition :)
rachelandrew commentedon Mar 1, 2019
I think this should be columns, I don't see any reason to say tracks, so I suggest that we edit this to say:
I'll add it to the agenda of a future call as it was put in there based on a resolution.
css-meeting-bot commentedon Mar 13, 2019
The CSS Working Group just discussed
pseudo-algorithm refers to "track size", terminology not already used in the spec, and agreed to the following:RESOLVED: Accept the change in https://github.com/w3c/csswg-drafts/issues/3649 (refer to columns not tracks)The full IRC log of that discussion
<dael> tOPIC: pseudo-algorithm refers to "track size", terminology not already used in the spec<dael> github: https://github.com//issues/3649
<dael> rachelandrew: Reading spec with authors. This is the first time track size mentioned in spec. Aim was to unify how sizing works but tracks isn't useful for multicol. Wanted to bring up since it was added with a resolution. I put sample wording in the issue
<dael> astearns: Not changing effect of resolution, just hte term?
<dael> rachelandrew: Yeah
<dael> florian: I've looked at that and if you assume tracks=columns it's clear but if you leave the two terms it confuses everything
<dael> astearns: Objections?
<fantasai> sgtm
<dael> RESOLVED: Accept the change in https://github.com//issues/3649 (refer to columns not tracks)