[css-overflow] Record issues about what max-lines applies to

Author: frivoal

css-overflow/Overview.bs

@@ -1078,7 +1078,15 @@ the ''continue/fragments'' value of the 'continue' property.
 	</dl>
 
 <p class="issue">Should this apply to fragment overflow only, or also
-to pagination?</p>
+to pagination?
+Given what we're doing with the continue property,
+it should actually apply to any fragmentainer.</p>
+
+Issue: having max-lines do nothing on regular elements is not ideal.
+When applied to non fragmentainers,
+it should probably cause 'continue' to compute to ''continue/discard''
+so that you only need to reach for one property rather than 2 to get
+that effect.
 
 	<div class="example">
 		<table class="source-demo-pair"><tr><td><pre>&lt;!DOCTYPE HTML&gt;

css-overflow/Overview.html

@@ -767,7 +767,7 @@
    <h1 class="p-name no-ref" id="title">CSS Overflow Module Level 3</h1>
 
    <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft,
-    <time class="dt-updated" datetime="2015-03-11">11 March 2015</time></span></h2>
+    <time class="dt-updated" datetime="2015-03-13">13 March 2015</time></span></h2>
 
    <div data-fill-with="spec-metadata">
     <dl>
@@ -2212,8 +2212,17 @@ <h3 class="heading settled" data-level="6.2" id="max-lines"><span class="secno">
    </dl>
 
 
-   <p class="issue" id="issue-1527f8dd"><a class="self-link" href="#issue-1527f8dd"></a>Should this apply to fragment overflow only, or also
-to pagination?</p>
+   <p class="issue" id="issue-f6e7b6c3"><a class="self-link" href="#issue-f6e7b6c3"></a>Should this apply to fragment overflow only, or also
+to pagination?
+Given what we’re doing with the continue property,
+it should actually apply to any fragmentainer.</p>
+
+
+   <p class="issue" id="issue-13fa8ed4"><a class="self-link" href="#issue-13fa8ed4"></a>having max-lines do nothing on regular elements is not ideal.
+When applied to non fragmentainers,
+it should probably cause <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> to compute to <a class="css" data-link-type="maybe" href="#valdef-continue-discard">discard</a>
+so that you only need to reach for one property rather than 2 to get
+that effect.</p>
 
 
    <div class="example">
@@ -2896,7 +2905,14 @@ <h2 class="no-num heading settled" id="issues-index"><span class="content">Issue
 				boundaries) is the break forced?
 			<a href="#issue-9488ec29"> ↵ </a></div>
    <div class="issue">Should this apply to fragment overflow only, or also
-to pagination?<a href="#issue-1527f8dd"> ↵ </a></div>
+to pagination?
+Given what we’re doing with the continue property,
+it should actually apply to any fragmentainer.<a href="#issue-f6e7b6c3"> ↵ </a></div>
+   <div class="issue">having max-lines do nothing on regular elements is not ideal.
+When applied to non fragmentainers,
+it should probably cause <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a> to compute to <a class="css" data-link-type="maybe" href="#valdef-continue-discard">discard</a>
+so that you only need to reach for one property rather than 2 to get
+that effect.<a href="#issue-13fa8ed4"> ↵ </a></div>
    <div class="issue">
 		This specification should define useful behavior
 		for all values of <a class="property" data-link-type="propdesc" href="#propdef-overflow">overflow</a> and <a class="property" data-link-type="propdesc" href="#propdef-continue">continue</a>