Skip to content

Commit 39ef6f5

Browse files
howcomhowcom
committed
adding last-call document
1 parent 39b5c5c commit 39ef6f5

1 file changed

Lines changed: 211 additions & 0 deletions

File tree

‎css3-multicol/last-call.html‎

Lines changed: 211 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,211 @@
1+
<!doctype html public '-//W3C//DTD HTML 4.01//EN'>
2+
3+
<title>CSS3 Multi-column layout &ndash; disposition of comments</title>
4+
<link rel=stylesheet href="../../StyleSheets/base.css">
5+
<style type="text/css">
6+
body { font-family: sans-serif; margin: 1em }
7+
8+
table {
9+
border-collapse: collapse; margin: 1em 0; empty-cells: show;
10+
}
11+
12+
th, td {
13+
text-align: left;
14+
vertical-align: top;
15+
border: thin solid black;
16+
padding: 0.2em;
17+
}
18+
19+
th { background: #eee }
20+
21+
pre {
22+
font-size: 0.8em;
23+
}
24+
25+
.proposal { background: orange }
26+
.rejected { background:red }
27+
28+
.source {
29+
background: silver;
30+
font-size: 1.2em;
31+
padding: 0.3em;
32+
}
33+
34+
.source a { text-decoration: none }
35+
36+
.a { background:lightgreen }
37+
.r { background:orange }
38+
.fo { background:red }
39+
</style>
40+
41+
42+
43+
<h1>CSS3 Multi-column Layout Module &ndash; disposition of comments</h1>
44+
45+
<p>Last call document: <a href="http://www.w3.org/TR/2009/WD-css3-multicol-20090630/">http://www.w3.org/TR/2009/WD-css3-multicol-20090630/</a>.
46+
47+
48+
<p>The following color coding convention is used for comments:</p>
49+
50+
<ul>
51+
<li class=a>The CSS WG agreed with the reviewer.
52+
<li class=r>The CSS WG disagreed with the reviewer.
53+
<li class=fo>The CSS WG disagreed with the reviewer and the reviewer raised a Formal Objection.
54+
</ul>
55+
56+
<!--
57+
<p>(There were no formal objections.)</p>
58+
-->
59+
60+
61+
62+
63+
http://lists.w3.org/Archives/Public/www-style/2009Jul/0003.html
64+
65+
66+
67+
<table>
68+
69+
<tr><th>#<th>Comment<th>Answer
70+
71+
72+
<tr><th colspan=3><a href="http://lists.w3.org/Archives/Public/www-style/2009Aug/0120.html">Comment</a> from Alex Mogilevsky on 2009-08-10
73+
74+
<tr class=a><td>
75+
76+
<p>Here is what I propose for floats in multicol:
77+
78+
<p>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.
79+
80+
<p>2) Leave definition of floats that intrude across columns to GCPM [2]. In fact, page floats as currently defined in GCPM are powerful enough to work as shown in [1].
81+
82+
<td><a href="http://lists.w3.org/Archives/Public/www-style/2009Sep/0186.html">Answer</a> on www-style
83+
84+
<tr><th colspan=3><a href="http://lists.w3.org/Archives/Public/www-style/2009Jul/0045.html">Comment</a> from Sylvain Galineau on 2009-07-14 (!)
85+
86+
<tr><td>
87+
In section 4, Column gaps and rules <a href="http://www.w3.org/TR/2009/WD-css3-multicol-20090630/#column-gaps-and-rules">[1]</a>:
88+
89+
<blockquote>"Column rules are only drawn between columns that have content."</blockquote>
90+
91+
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.
92+
93+
<p>[1] http://www.w3.org/TR/2009/WD-css3-multicol-20090630/#column-gaps-and-rules
94+
95+
<td><a href="http://lists.w3.org/Archives/Public/www-style/2009Oct/0116.html">Followup on www-style</a>
96+
97+
<tr><th colspan=3><a href="http://lists.w3.org/Archives/Public/www-style/2009Jul/0003.html">Comment</a> from Bert Bos on 2009-07-01
98+
99+
<tr class=a><td>I just noticed that there is still an example (example VI) in the
100+
non-normative section 1 that we forgot to delete, when we removed
101+
the 'column-break-*' properties from the draft.
102+
103+
<td>editorial, fixed
104+
105+
<tr><th colspan=3><a href="http://lists.w3.org/Archives/Public/www-style/2009Jul/0000.html">Comment</a> from Giovanni Campagna on 2009-07-01
106+
107+
<tr class=a><td>The title is still "CSS3 module: Multi-column layout"
108+
109+
<p>Hadn't the WG decided to adopt consistent naming and in particular to
110+
avoid saying CSS3?
111+
112+
<p>If yes, it should be called "CSS Multi-column Layout Module" or "CSS
113+
Multi-column Layout Module Level 3" (although I guess that Level 3 is
114+
only for features that did exist in level 2)
115+
116+
<td>Yes, the title should be aligned with the other names. "CSS Multi-column Layout Module" is a fitting name, as there is no previous level for multi-column layout.
117+
118+
<tr class=r><td>About column-rule-color:
119+
Why UAs are required only to support CSS2 colors?
120+
If the goal is to avoid the burden of hsl / rgba / SVG colors,
121+
shouldn't that be delegated to a reduced profile?
122+
123+
<td>This is a general problem for several CSS modules; should they refer to CSS 2.1 or emerging CSS3 modules? In this case, it seems best to refer to CSS 2.1 and the draft has been edited to reflect this.
124+
125+
<tr class=a><td>About column breaks:
126+
127+
At the beginning of section 5, replace desrciption with description
128+
129+
<td>editorial
130+
131+
<tr><td>About column breaks: Is it possible to avoid a column break while still allow a page break?
132+
Is the intended effect like:
133+
134+
<pre>
135+
----------------------------------
136+
| a bcd efg hij | |
137+
| lmn opq rst u | |
138+
139+
/ page break, but content remains
140+
in the same column /
141+
142+
| rst uvw xyz ab| |
143+
| cde fgh ijk l | |
144+
----------------------------------
145+
</pre>
146+
147+
<td>A page break will always cause a column break; columns on different pages are considered to be different columns. This specification does not provide a way to ensure that all content is in the (say) left-most column.
148+
149+
<tr><td>About column breaks: What about margin and collapsing of them?
150+
If you're delegating all (not just properties) to css3-page, you
151+
should say that explicitly.
152+
153+
<td>The specification states:
154+
155+
<blockquote>
156+
A multi-column element establishes a new block formatting context, as per CSS 2.1 section 9.4.1.
157+
</blockquote>
158+
159+
Which is correct, but somewhat cryptic. Therefore one example has been added:
160+
161+
<blockquote>
162+
A top margin set on the first child element of a mulitcol element will not collase with the margins of the multicol element.
163+
</blockquote>
164+
165+
Further, in the description of the "break" properties, this text now occurs:
166+
167+
<blockquote>
168+
When a page or column break splits a box, the box's margins, borders, and padding have no visual effect where the split occurs. However, margins will be preserved after forced page/column break. A forced page/colum break is a break that does not occur naturally.
169+
<blockquote>
170+
171+
172+
<tr class=a><td>About overflow inside and outside the multicolum element:
173+
174+
you should insert some examples of non-floated, overflowing,
175+
clipped element (maybe inlines with long words)
176+
177+
<td>
178+
179+
An image with has been added.
180+
181+
<tr><td>About overflow inside and outside the multicolum element:
182+
183+
what happens if a non-floated element overflows vertically?
184+
Is it still clipped regardless of overflow? Can implementations put
185+
scrollbars, if overflow asks so?
186+
187+
<td>Yes, the spec states
188+
189+
<blockquot
190+
Content that extend outside column boxes at the edges of the multi-column element is clipped according to the 'overflow' property.
191+
192+
193+
<tr><td>About overflow inside and outside the multicolum element:
194+
195+
what happens if Example XVIII has an element that floats on
196+
the rigth? Is the element clipped (showing only the right part), does
197+
the element intrude (ignoring the side of the float), does overflow
198+
apply?
199+
200+
<tr><td>About overflow inside and outside the multicolum element:
201+
202+
if there are more columns than available, are scrollbars
203+
rendered when overflow:auto / scroll?
204+
205+
<tr><td>Section conformance names a "column-grid-image", but no definition
206+
is provided in the document.
207+
208+
<td>I assume you refer to 'column-gap-image'. Indeed, this should be removed.
209+
210+
211+
</table>

0 commit comments

Comments
 (0)