Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[css-multicol] Text describing column boxes as block container boxes #1738
On 1 Dec 2011, Anton Prowse raised a bunch of issues with the Multicol CR. One of which was:
There was a minor edit made to the spec - email 9 Jan 2012. This seems to be the current wording.
Issue was returned to 15 April 2013 with a suggestion that the wording be revised again, as far as I can see that didn't happen and I'm posting this to see if anyone has an opinion on the matter now.
This is one of a list of legacy issues I'm digging out of the www-style archives.
Relevant section of the spec is here https://www.w3.org/TR/css-multicol-1/#the-multi-column-model the wording is under Example 9:
In the email of 15 April are suggestions to reword this, excerpt as follows, I hope I am attributing quotes to correct people, but I thought I'd save everyone digging through this:
Håkon Wium Lie, responded:
Anton Prowse also wrote:
Håkon Wium Lie responded:
The question to the WG is do we want to remove either or both of these sentences as per this discussion?
The Working Group just discussed
The full IRC log of that discussion<eae> Topic: Text describing column boxes as block container boxes
<eae> github issue: https://github.com//issues/1738
<eae> rachelandrew: This is another text change for column boxes. Basically there is a section in the spec, example 9, about container boxes.
<eae> rachelandrew: There was a proposal to have the second sentence to be omitted.
<eae> rachelandrew: There was no objections yet no edit took place. Looks like it was dropped.
<eae> rachelandrew: Idea of containing block not defined in spec.
<eae> TabAtkins: I agree, go ahead and kill second sentence
<TabAtkins> Kill "That is, column boxes behave like block-level, table cell, and inline-block boxes as per CSS 2.1, section 10.1, item 2 [CSS21]."
<eae> rachelandrew: Should we remove either or both of these sentences?
<eae> florian: Remove 2nd and 3rd?
<eae> fantasai: I don't think we should remove the 3rd.
<eae> TabAtkins: Default case applies.
<eae> florian: This might be read as shutting down other properties that could apply unless specified.
<eae> fantasai: Behavior when you apply position relative needs to be defined
<eae> TabAtkins: doesn't turn column boxes into abs containig blocks is fine, makes sense, should be explicitly informative. As written it is bad and should be removed.
<eae> rachelandrew: A clarification would be useful.
<eae> fantasai: It might help to clarify that the multicol container is the principle box, not mentioned in spec, and that the column boxes are anonymous.
<eae> fantasai: For example pos relative doesn't apply to column box.
<eae> rachelandrew: Makes sense to me
<eae> Rossen: Super good clarification. We all know this yet it isn't mentioned anywhere.
<eae> Rossen: Common source of confusion
<eae> rachelandrew: What are we suggesting to remove here? Turn third sentence into a note?
<eae> TabAtkins: Yes, and also make it clear that it clarifies that nothing you do on the column box...
<eae> fantasai: The part about being a principle box should go in sentence two. We should fix that.
<eae> fantasai: We don't have a good term for that box now, we refer to it as the multicol element, separate issue.
<eae> gregwhitworth: One thing that would be beneficial is having an example in there. Saying principle box isn't necessarily going to help web developers clarify.
<eae> Rossen: Similar to the table example in 2.1, speaks volumnes when people see it
<eae> Proposed resolution: Remove sentence 2 and 3 and adding clarification about the principle box.
<eae> RESOLVED: Remove sentence 2 and 3 and adding clarification about the principle box.