[css-overflow-3] Refer to open github issues from the spec

Author: frivoal

css-overflow-3/Overview.bs

@@ -35,6 +35,8 @@ spec:css-transforms-2; type:property; text:transform-style
 type: dfn; spec:css-multicol-1; text:overflow column
 type: dfn; spec:css-transforms-2; text:3d rendering context
 spec:css-writing-modes-4; type:dfn; text:end
+spec:css-pseudo-4; type:selector; text:::first-line
+spec:css-pseudo-4; type:selector; text:::first-letter
 </pre>
 <!-- FIXME: the break-* link doesn't actually work! -->
 <pre class="anchors">
@@ -795,6 +797,13 @@ Indicating Block-Axis Overflow: the 'block-overflow' property</h3>
 		Computed value: specified value
 	</pre>
 
+	Issue(2561): The names of this property and its values are not fully settled,
+	and alternatives have been suggested.
+	For the time being,
+	experiemental implementations are encouraged
+	to follow the full behavior defined by this property,
+	but to only expose it to authors through its 'line-clamp' shorthand.
+
 	This property allows inserting content into the last line box
 	before a (forced <em>or</em> unforced) <a>region break</a>
 	to indicate the continuity of truncated/interrupted content.
@@ -853,6 +862,8 @@ Indicating Block-Axis Overflow: the 'block-overflow' property</h3>
 	and measures the inserted <a>block overflow ellipsis</a>
 	together with the rest of the line’s content.
 
+	Issue(2906): Interaction with ''::first-letter'' and ''::first-line'' needs to be defined.
+
 	If there is no next <a>fragmentation container</a>
 	and thus the remainder of the content after the break would be discarded,
 	then the UA may visually replace the contents of the line,
@@ -866,13 +877,20 @@ Indicating Block-Axis Overflow: the 'block-overflow' property</h3>
 	This can result in changes to layout within or impacted by the line.
 	The means of breaking any resulting cycles is up to the UA.
 
+	Issue(2905): We may want to get rid of the "MAY" in the previous paragraph,
+	and require a single behavior.
+	Finding how to break the cycles probably should be defined as well.
+
 	If the <a>block overflow ellipsis</a>
 	is too long to fit in the line,
 	the result is undefined.
 	(The UA may, for example, treat the <a>block overflow ellipsis</a> as an unbreakable string,
 	or it may lay out the string across more than one line,
 	replacing content in earlier lines as well.)
 
+	Issue(2882): There is a suggestion to actually define the behavior
+	when the ellipsis is too long to fit the line.
+
 	The <a>block overflow ellipsis</a> does not capture events:
 	pointer events are dispatched to whatever is underneath
 	or otherwise visually replaced by it.
@@ -1103,9 +1121,10 @@ Once it is sufficiently stable in this specification,
 			similar to if it were ''display: none'':
 			* Just as the content is visually hidden, it is not made available for speech rendering
 			* It does not allow user interaction
+			* Issue(2970): Mae sure effects on OM are well defined
 			* [=Positioned=] elements whose static position is in the discarded content are not rendered.
 
-				Issue: Are we sure about that?
+				Issue(2971): Are we sure about that?
 				Discussions in the <a href="https://lists.w3.org/Archives/Public/www-style/2018Jul/0030.html">Syndey F2F meeting</a>
 				seemed to generally converge on this,
 				but other possibilities were raised.
@@ -1119,6 +1138,8 @@ Once it is sufficiently stable in this specification,
 			<a lt="min-content inline size">min-content</a> and <a>max-content</a> <a>inline sizes</a>
 			(see [[css-break-3#varying-size-boxes]]).
 
+			Issue(2945): The effect on intrinsic sizing is under discussion.
+
 			The effect on [=multi-column containers=] is to discard any [=overflow column=].
 
 			Note: In the case of <a href="https://www.w3.org/TR/css-break-3/#parallel-flows">parallel fragmentation flows</a>,