adding resolutions from CSSWG meeting

Author: howcom

css3-multicol/Overview.src.html

@@ -23,6 +23,36 @@
 
 <!--logo-->
 
+<!--
+
+   - RESOLVED: page-break-before, page-break-after: column to force column breaks,
+               other values apply to column breaking as well as pages
+
+   - RESOLVED: howcome to clearly distinguish GCPM features that are moving forward,
+               then propose publishing a new WD
+
+   - RESOLVED: New syntax is image-resolution: normal | [ <dpi> || auto ]
+     RATIONALE: Removes unused combinations and unnecessary comma
+
+   - RESOLVED: Replace image-resolution: auto; with image-resolution: from-image;
+     RATIONALE: 'auto' vs. 'normal' is hard to understand. ('normal' is 1 pixel == 1px)
+
+   - RESOLVED: URLs inside functional notation where URL is expected should be able
+               to take either url() or bare strings (like @import), preference for
+               examples is bare strings.
+
+   - Discussed removing 'background-image-resolution' in favor of various options.
+     So far idea is that 'image-resolution' applies to all images and we will
+     introduce functional notation in the future to allow setting resolution on a
+     per-image basis.
+
+   - howcome to prepare css3-multicol for Last Call publication; expecting a long
+     (8 weeks) LC period to elicit comments and clarifications
+
+   - Margins of multicol element no longer collapse with first/last children
+
+-->
+
 <h1>CSS3 module: Multi-column layout</h1>
 
 <h2 class="no-num no-toc" id="w3c-working">[LONGSTATUS] [DATE]</h2>
@@ -1040,102 +1070,38 @@ <h2>Column breaks</h2>
 <p>When content is laid out in multiple columns, the user agent must
 determine where column breaks are placed. The problem of breaking
 content into columns is similar to breaking content into pages. CSS3
-Paged Media [[!CSS3PAGE]] describes rules for breaking content into
-pages. This specification prescribes the same rules for column breaks,
-with the following differences:
-
-<ul>
-
-<li>The properties for indicating column breaks are
-'column-break-before' and 'column-break-after' (instead of
-'page-break-before' and 'page-break-after'). The 'page-break-inside'
-property can be used to indicate that a column break should be avoided
-inside the element.
+Paged Media [[!CSS3PAGE]] describes properties and rules for breaking
+content into pages, and the same properties and rules are used for
+breaking columns. 
 
-<li>A page break will always cause a column break; the opposite is not
-the case. Consequently, when both a page break and a column break is
-specified, a page break will occur.
-
-</ul>
-
-<p class="issue">Should we reuse 'page-break-before' and
-'page-break-after' instead of creating two new properties? A new
-keyword ''column'' would be added to these properties to force column
-breaks.
-
-<p>Also, margins will be set to zero around column breaks, just like
-for page breaks.
+<p>A new keyword, ''column'' is introduced on 'page-break-before' and
+'page-break-after'. This keyword forces a column before or after the
+element, just like the ''always'' keyword forces page breaks.
 
+<div class="example">
 
-<h3>'column-break-before'</h3>
-
-<table class=propdef>
-    <tr>
-      <td><em>Name:</em>
-      <td><dfn>column-break-before</dfn>
-    <tr>
-      <td><em>Value:</em>
-      <td>auto | always | avoid
-    <tr>
-      <td><em>Initial:</em>
-      <td>auto
-    <tr>
-      <td><em>Applies to:</em>
-      <td>block-level elements
-    <tr>
-      <td><em>Inherited:</em>
-      <td>no
-    <tr>
-      <td><em>Percentages:</em>
-      <td>N/A
-    <tr>
-      <td><em>Media:</em>
-      <td>visual
-    <tr>
-      <td><em>Computed&nbsp;value:</em>
-      <td>as specified
-</table>
+<p>In this example, forced column breaks appear before <code>h2</code>
+elements and after <code>img</code> elements:
 
+<pre>
+.multicol { colum-width: 8em }
+.multicol h2 { page-break-before: column }
+.multicol img { page-break-after: column }
+</pre>
 
-<h3>'column-break-after'</h3>
+</div>
 
-<table class=propdef>
-    <tr>
-      <td><em>Name:</em>
-      <td><dfn>column-break-after</dfn>
-    <tr>
-      <td><em>Value:</em>
-      <td>auto | always | avoid
-    <tr>
-      <td><em>Initial:</em>
-      <td>auto
-    <tr>
-      <td><em>Applies to:</em>
-      <td>block-level elements
-    <tr>
-      <td><em>Inherited:</em>
-      <td>no
-    <tr>
-      <td><em>Percentages:</em>
-      <td>N/A
-    <tr>
-      <td><em>Media:</em>
-      <td>visual
-    <tr>
-      <td><em>Computed&nbsp;value:</em>
-      <td>as specified
-</table>
+<p>The 'page-break-inside' property specifies the behavior of natural
+column breaks inside elements.
 
-<p>Values for these properties have the following meanings:
+<div class="example">
+<pre>
+.multicol p { page-break-inside: avoid }
+</pre>
+</div>
 
-<dl>
-<dt>auto
-<dd>Neither force nor forbid a column break before / after / inside the generated box. 
-<dt>always 
-<dd>Always force a column break before / after the generated box. 
-<dt>avoid 
-<dd>Avoid a column break before / after / inside the generated box. 
-</dl>
+<p>Margins will be set to zero around column breaks, just like for
+page breaks.
 
 
 <h2>Spanning columns</h2>