[css-overflow] record issue about multicol

Author: frivoal

css-overflow/Overview.bs

@@ -554,6 +554,11 @@ This was initially proposed as
 "fragmentation: auto | none | break | clone | page"
 in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>.
 
+Issue: If we introduce a pseudo element that can select columns in a multicol,
+we would need to specify that next computes to next on it,
+or introduce a new value and have next compute to that
+(but what would that value compute to on things that aren't columns?).
+
 Note: For background discussions leading to this property, see these threads:
 <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussion of overflow, overflow-x, overflow-y and overflow-style</a> and
 <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">proposal for a fragmentation property</a>

css-overflow/Overview.html

@@ -950,6 +950,12 @@ <h2 class="heading settled" data-level="4" id="fragmentation"><span class="secno
 in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>.</p>
 
 
+   <p class="issue" id="issue-598fb492"><a class="self-link" href="#issue-598fb492"></a>If we introduce a pseudo element that can select columns in a multicol,
+we would need to specify that next computes to next on it,
+or introduce a new value and have next compute to that
+(but what would that value compute to on things that aren’t columns?).</p>
+
+
    <p class="note" role="note">Note: For background discussions leading to this property, see these threads:
 <a href="http://lists.w3.org/Archives/Public/www-style/2012May/1197.html">discussion of overflow, overflow-x, overflow-y and overflow-style</a> and
 <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">proposal for a fragmentation property</a></p>
@@ -2134,6 +2140,10 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
 This was initially proposed as
 "fragmentation: auto | none | break | clone | page"
 in <a href="https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html">https://lists.w3.org/Archives/Public/www-style/2015Jan/0357.html</a>.<a href="#issue-77a336c3"> ↵ </a></div>
+   <div class="issue">If we introduce a pseudo element that can select columns in a multicol,
+we would need to specify that next computes to next on it,
+or introduce a new value and have next compute to that
+(but what would that value compute to on things that aren’t columns?).<a href="#issue-598fb492"> ↵ </a></div>
    <div class="issue">Write this section<a href="#issue-001d5014"> ↵ </a></div>
    <div class="issue">The initial proposal in <a data-link-type="biblio" href="#biblio-css3gcpm">[CSS3GCPM]</a> and implemantation from Opera
 used 4 values instead of <a class="css" data-link-type="maybe" href="#valdef-continue-paginate">paginate</a>: