Last call document: http://www.w3.org/TR/2009/WD-css3-multicol-20090630/.
Editor's draft: http://dev.w3.org/csswg/css3-multicol
The following color coding convention is used for comments:
(There were no formal objections.)
|Comment from Alex Mogilevsky on 2009-08-10|
Here is what I propose for floats in multicol:
1) In [multicol] spec, remove special treatment for overflow of floats. Overflow floats should be clipped to the column exactly as any other kind of overflow would. This way, content that was initially designed for single-column layout has same behavior.
2) Leave definition of floats that intrude across columns to GCPM . In fact, page floats as currently defined in GCPM are powerful enough to work as shown in .
|There have been no implementations of intrusions, so it seems best to removed them when going to CR.||Answer on www-style|
|Comment from Sylvain Galineau on 2009-07-14 (!)|
In section 4, Column gaps and rules :
Assuming column 2's entire content did not fit e.g. an image and needs to overflow to the next page, I assume column 2 is considered to have content in this case.
|Answer on www-style, followup from Sylvain, final message from howcome|
|Comment from Bert Bos on 2009-07-01|
|I just noticed that there is still an example (example VI) in the non-normative section 1 that we forgot to delete, when we removed the 'column-break-*' properties from the draft.||editorial||fixed|
|Comment from Giovanni Campagna on 2009-07-01|
|The title is still "CSS3 module: Multi-column layout"
Hadn't the WG decided to adopt consistent naming and in particular to avoid saying CSS3?
If yes, it should be called "CSS Multi-column Layout Module" or "CSS Multi-column Layout Module Level 3" (although I guess that Level 3 is only for features that did exist in level 2)
|New title: CSS Multi-column Layout Module||howcome Giovanni howcome|
|About column-rule-color: Why UAs are required only to support CSS2 colors? If the goal is to avoid the burden of hsl / rgba / SVG colors, shouldn't that be delegated to a reduced profile?||The CSS WG chose to point to refer to CSS 2.1 instead of creating a reduced profile. This was accepted by Giovanni.||howcome Giovanni howcome|
|About column breaks: At the beginning of section 5, replace desrciption with description||editorial||howcome Giovanni howcome|
|About column breaks: Is it possible to avoid a column break while still allow a page break?
Is the intended effect like:
---------------------------------- | a bcd efg hij | | | lmn opq rst u | | / page break, but content remains in the same column / | rst uvw xyz ab| | | cde fgh ijk l | | ----------------------------------
|howcome Giovanni howcome|
|About column breaks: What about margin and collapsing of them? If you're delegating all (not just properties) to css3-page, you should say that explicitly.||howcome Giovanni howcome|
|About overflow inside and outside the multicolum element: you should insert some examples of non-floated, overflowing, clipped element (maybe inlines with long words)||howcome Giovanni howcome|
|About overflow inside and outside the multicolum element: what happens if a non-floated element overflows vertically? Is it still clipped regardless of overflow? Can implementations put scrollbars, if overflow asks so?||howcome Giovanni howcome|
|About overflow inside and outside the multicolum element: what happens if Example XVIII has an element that floats on the rigth? Is the element clipped (showing only the right part), does the element intrude (ignoring the side of the float), does overflow apply?||intrusion has been removed||howcome Giovanni howcome|
|About overflow inside and outside the multicolum element: if there are more columns than available, are scrollbars rendered when overflow:auto / scroll?||howcome Giovanni howcome|
|Section conformance names a "column-grid-image", but no definition is provided in the document.||a spurious reference to 'column-gap-image' has been removed||howcome Giovanni howcome|