[css-multicol] reverting the change made to column-fill in w3c#3224

CSS WG resolution in w3c#4036 was to revert this change and add an issue to the spec referencing this as an open issue.

Author: rachelandrew

css-multicol-1/Overview.bs

@@ -1256,14 +1256,7 @@ Filling Columns</h2>
 		</dd>
 	</dl>
 
-	In continuous contexts, 
-	this property will only be consulted if the length of columns has been constrained in the block dimension,
-	including min and max constraints (e.g., 'height', 'min-height', 'max-height'). 
-	Otherwise, columns will automatically be balanced.
-
-	<wpt>
-	multicol-fill-auto-003.xht
-	</wpt>
+	Issue: We need to define the behavior of ''column-fill'' in continuous contexts. A previous resolution (<a href="https://github.com/w3c/csswg-drafts/issues/3224#issuecomment-468089503">3224</a>) defined that the property should only be consulted if the length of columns was constrained in the block dimension. This was reverted in (<a href="https://github.com/w3c/csswg-drafts/issues/4036#issuecomment-531646703">4036</a>) pending further discussion.
 
 	In continuous contexts, this property does not have any effect when there are overflow columns.
 
@@ -1533,7 +1526,6 @@ This appendix is <em>informative</em>.
 	<br />"In a multi-column formatting context the used value of normal for the column-gap property is 1em. This ensures columns are readable when the initial values are used. If there is a column rule between columns, it will appear in the middle of the gap." <a href="https://github.com/w3c/csswg-drafts/issues/3641">Resolved 4 June 2019.</a></li>
 	<li>Reworded the section <a href="#the-multi-column-model">The multi-column model</a>, based on input from Morten Stenshorne in <a href="https://github.com/w3c/csswg-drafts/issues/2203#issuecomment-431695940">issue 2203</a>.</li>
 	<li>Removed the at-risk marker from the length-percentage value for 'column-gap'. <a href="https://github.com/w3c/csswg-drafts/issues/3988">Resolved 4 June 2019.</a></li>
-	<li>Added the paragraph "In continuous contexts, this property will only be consulted if the length of columns has been constrained in the block dimension, including min and max constraints (e.g., 'height', 'min-height', 'max-height'). Otherwise, columns will automatically be balanced." This paragraph (without the additional detail regarding min and max constraints) was commented out in 2012, causing an interoperability issue. Also corrected the example of content ending up all in the first column, by adding the height constraint. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/3224#issuecomment-468089503">28 February 2019</a></li>
 	<li>Updated the introduction to remove mention of the benefits of multicol over using tables for layout and instead refer to the unique characteristics of multicol. Editorial change referenced in <a href="https://github.com/w3c/csswg-drafts/issues/3654">issue 3654</a>.</li>
 	<li>Changed the sentence added in the pseudo-algorithm section after the 7 Jan 2016 resolution, to refer to <em>columns</em> and not <em>tracks</em> as tracks are not defined in this specification. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/3649#issuecomment-472505520">13 March 2019</a>.</li>
 	<li>Changes and clarifications to the SVG images used in the specification.</li>