grid spec update in progress; current comments are incorporated

alexmog1 · alexmog1 · commit ad53e78a180b · 2008-01-14T18:38:11.000Z
diff --git a/css3-grid/overview.src.html b/css3-grid/overview.src.html
@@ -4,7 +4,7 @@
 <head>
   <meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
   <title>CSS Grid Positioning Module Level 3</title>
-  <link rel="stylesheet" type="text/css" href="default.css">
+  <link rel="stylesheet" type="text/css" href="../default.css">
 
   <style type="text/css">
     .cols { width: 500px; height: 200px; background: #fff; position: relative; border: solid 10px blue; margin: 0.5em 2em 1em 0; font: bold 14px/19px Arial, sans-serif }
@@ -377,59 +377,17 @@ <h4>Table</h4>
 <p class="issue">Definition of a grid for a table is only meaningful if there is 
 something that can use it. Currently there are no table floats. Should there be? 
 Something like &quot;float:top left table; float-offset:2gr 4gr&quot; would use the table 
-grid. Is there a use case for such floats?</p>
+grid. Is there a use case for such floats? There is still absolute positioning 
+that can target at table of course...</p>
 
+<h4>Viewport</h4>
+<p>Viewport always defines a single-cell grid with the size of the viewport. </p>
 <h4>Priority
 of explicit grid definition</h4>
 
 <p>If explicit grid properties grid-columns or grid-rows are
-specified on an element with an implicit grid the explicit properties have
+specified on an element with an implicit grid, the explicit properties have
 priority.</p>
-<p>&nbsp;</p>
-<p class="todo">editing work in progress... continue editing from here down...</p>
-
-<h2>Grid container</h2>
-
-<p>Using grid does not require any new rules on how the
-positioning container is determined. When grid units are used with all
-applicable sizing positioning methods, the grid is always taken from the
-applicable containing block (which is found as defined as defined in CSS2.1
-section 10.1).</p>
-
-<p>In this example, div1 is the positioning parent and
-therefore grid of div1 is used for positioning:</p>
-
-<div class="example">
-<pre>&lt;style&gt;
- <strong>.div1 { position:absolute; grid-columns:4.5em (1em 4.5em); }</strong> /* this grid is used */
- .div2 { columns-width:10em; column-gap:1em; } 
- img { position:absolute; left:2gr; width:3gr; }
-&lt;/style&gt;
-&lt;div class=&quot;div1&quot;&gt;
- &lt;div class=&quot;div2&quot;&gt;
-  &lt;img /&gt;
- &lt;/div&gt;
-&lt;/div&gt;
-</pre>
-</div>
-
-<p>However in the next example, grid of div2 is used by the float, because it is 
-the float&#39;s containing block:</p>
-
-<div class="example">
-<pre>&lt;style&gt;
- .div1 { position:absolute; grid-columns:4.5em (1em 4.5em); }
- <strong>.div2 { columns-width:10em; column-gap:1em; }</strong> /* this grid is used */
- img { float:left; float-offset:2gr; width:3gr; }
-&lt;/style&gt;
-&lt;div class=&quot;div1&quot;&gt;
-  &lt;div class=&quot;div2&quot;&gt;
-   &lt;img /&gt;
-  &lt;/div&gt;
-&lt;/div&gt;
-</pre>
-</div>
-
 
 
 <h2>Grid units</h2>
@@ -530,20 +488,58 @@ <h3>Applicability of grid units</h3>
 in the direction of line progression (horizontal in layout with horizontal 
 lines).</p>
 <p>Grid units never apply to inline elements, including inline blocks.</p>
+
+
+<h3>Grid container</h3>
+
+<p>Since separate grids can be defined on nested elements, it must be defined 
+which grid is referred to for every use of &#39;gr&#39; unit.</p>
+<p>For all cases where &#39;gr&#39; unit is applicable the grid is taken from the
+containing block (which is found as defined as defined in CSS2.1
+section 10.1).</p>
+
+<p>In this example, div1 is the positioning parent and
+therefore grid of div1 is used for positioning:</p>
+
+<div class="example">
+<pre>&lt;style&gt;
+ <strong>.div1 { position:absolute; grid-columns:4em repeat(1em 4em); }</strong> /* this grid is used */
+ .div2 { columns-width:10em; column-gap:1em; } 
+ img { position:absolute; left:2gr; width:3gr; }
+&lt;/style&gt;
+&lt;div class=&quot;div1&quot;&gt;
+ &lt;div class=&quot;div2&quot;&gt;
+  &lt;img /&gt;
+ &lt;/div&gt;
+&lt;/div&gt;
+</pre>
+</div>
+
+<p>However in the next example, grid of div2 is used by the float, because it is 
+the float&#39;s containing block:</p>
+
+<div class="example">
+<pre>&lt;style&gt;
+ .div1 { position:absolute; grid-columns:4.5em (1em 4.5em); }
+ <strong>.div2 { columns-width:10em; column-gap:1em; }</strong> /* this grid is used */
+ img { float:left; float-offset:2gr; width:3gr; }
+&lt;/style&gt;
+&lt;div class=&quot;div1&quot;&gt;
+  &lt;div class=&quot;div2&quot;&gt;
+   &lt;img /&gt;
+  &lt;/div&gt;
+&lt;/div&gt;
+</pre>
+</div>
+
+
 <h3>Reference point for grid units</h3>
-<p class="issue"><strong>ISSUE: </strong>Calculating grid units require a 
+<p class="issue">Calculating grid units require a 
 reference point within the grid and direction. This needs a precise definition. 
 For the same element, grid units for position and size may have different 
 reference points (but probably not different directions).</p>
-<h3>Undefined grid units</h3>
-<p>Because of positional nature of &#39;gr&#39; unit it is ambiguous in absence
-of position. Also, grid size may not be defined when a grid unit has to be 
-applied.</p>
-<p>In such case values specified in &#39;gr&#39; units are 
-ignored (set to their initial value).</p>
-<p class="issue">Need some examples here. E.g. what happens to &#39;1gr&#39; float in a 
-multi-column element within a table that is sized to content? Grid size depends 
-on the float&#39;s size so &#39;gr&#39; should be ignored.</p>
+<p class="issue">Define how &#39;gr&#39; is used on in-flow blocks. Is &#39;1gr&#39; generally 
+equivalent to &#39;100%&#39; there?</p>
 
 <h2>Grid in overflow</h2>
 <p>When a measure defined in grid units extends outside the boundaries of grid 
@@ -558,11 +554,6 @@ <h2>Grid in overflow</h2>
 			<li>Otherwise, the last column or row size is repeated </li>
 		</ul>
 		</li>
-		<li>Default grid<ul>
-			<li>Same as non-repeating pattern: equally spaced lines are added, 
-			separated by the size of the element</li>
-		</ul>
-		</li>
 		<li>Multi-column element<ul>
 			<li>Additional (gap, column) pairs are added.
 			<ul>
@@ -577,6 +568,11 @@ <h2>Grid in overflow</h2>
 			<li>The last column is repeated</li>
 		</ul>
 		</li>
+		<li>Viewport<ul>
+			<li>Additional lines are added, separated by the size of the 
+			viewport</li>
+		</ul>
+		</li>
 	</ul>
 	</li>
 	<li>If overflow is in negative direction<ul>
@@ -586,34 +582,39 @@ <h2>Grid in overflow</h2>
 	</li>
 </ul>
 
-<p class="issue">TODO: example</p>
+<p class="issue">Add an example</p>
+<p class="issue">How important is an overflow grid? What use cases would suffer 
+if &#39;gr&#39; is just set to zero in overflow?</p>
 
 <h2>Issues</h2>
 
-<h3>Containing block</h3>
-<p>Does a grid (implicit or explicit) add another definition to &quot;containing 
-block&quot;? It would be great to say No and keep unit definition separate from 
-choice of sizing/positioning container.</p>
+<h3>Grid on shrink-to-fit elements</h3>
+<p class="issue">Specifying a grid on an element with shrink-to-fit sizing can 
+create difficult or unsolvable problems, similar to use percentages within 
+shrink to fit but even more complicated. Consider ignoring grid definition on 
+anything shrink-to-fit.</p>
 <h3>Additional implicit grid lines</h3>
-<p class="MsoNormal"><span style="color:#1F497D">On the implicit grids for 
+<p class="issue">On the implicit grids for 
 multi-column elements, it might be useful to have one grid line on the left and 
 right edge of each column, as well as a single grid line between each pair of 
 columns. Perhaps doing the same thing for tables, one line on each side of the 
-border spacing and another at the row/column boundary.<o:p></o:p></span></p>
+border spacing and another at the row/column boundary.</p>
 <h3>Snap to grid</h3>
 
 <p class="issue">Should there be an option to align flow content to next
 available gridline? It opens really cool scenarios. But are they compelling
 enough to create a next available notion?</p>
 
-<h3>Default grid</h3>
-<p>When a grid unit is used in context where there isn&#39;t an explicit or implicit 
-grid specified, what should it be? Reaching to nearest parent with a defined 
-grid may or may not be the right choice. There is an option to give any element 
-a &quot;default grid&quot; of one cell, but that can make nesting scenarios more 
-complicated.</p>
-<h3>Facing pages</h3>
-<p>It must be possible to define different grids for left and right pages</p>
+<h3>Undefined grid and notion of &#39;default&#39; grid</h3>
+<p class="issue">When a grid unit is used in context where there isn&#39;t an 
+explicit or implicit grid specified, what should it be? Reaching to nearest 
+parent with a defined grid may or may not be the right choice. There is an 
+option to give any element a &quot;default grid&quot; of one cell.</p>
+<h3>Page grid</h3>
+<p>It must be possible to define different grids for left and right pages. Also, 
+any page with different dimensions (such as named pages) should be able to 
+define its own grid. </p>
+<p class="issue">Add grid-columns/grid-rows to @page rule</p>
 <h3>Named grid lines and cells</h3>
 
 <p class="issue">If grid is used extensively, named grid locations would be 
@@ -641,7 +642,8 @@ <h3>Templates in CSS3 Advanced Layout module</h3>
 <h2 class="no-num" id=acknowledgments>Acknowledgments</h2>
 
 <p class="MsoNormal">This specification is made possible by input from Håkon 
-Wium Lie, Steve Zilles, Mike Duggan, Bill Hill, Geraldine Wade, Rikkert Koppes, [to be added].</p>
+Wium Lie, Steve Zilles, Mike Duggan, Bill Hill, Geraldine Wade, Rikkert Koppes, 
+Peter Linss [to be added].</p>
 <p>Thanks to Khoi Vinh for the “Yeeaahh!” Example.</p>
 
 <p>&nbsp;</p>
