[css-tables] Continue to transfer issues to GH

Author: Greg Whitworth

css-tables-3/Overview.bs

@@ -254,13 +254,7 @@ spec:css21; type:property; text:max-width
 
 			</dl>
 
-			<p class="issue">
-				We should define the table grid, table grid rows, table grid columns, 
-					and in general what spanning means for table-cells 
-					(e.g. a rowspanning table-cell, a colspanning table-cell, etc).
-				Inspiration can be taken from 
-					<a href="https://drafts.csswg.org/css-grid/#grid-concepts">CSS Grid</a> and/or 
-					<a href="https://html.spec.whatwg.org/#table-processing-model">HTML</a>.
+			ISSUE(603): Define the table grid
 
 
 	<!--------------------------------------------------------------------------------->
@@ -306,15 +300,8 @@ spec:css21; type:property; text:max-width
 							are the first and/or last child of a <a>tabular container</a>,
 							and whose immediate sibling (if any) is a <a>table-non-root</a> box,
 							are treated as if they had <code>display: none</code>.
-							<div class="issue">
-								This (combined with previous rule) is a breaking change from <a href="https://drafts.csswg.org/css2/tables.html#anonymous-boxes">CSS 2.1</a>.
-								Edge is the only implementation of the complex version so we might as well drop it.
-								The spec now covers Firefox behavior.
-								Chrome collapses everything which is a bug anyway.
-								<a href="https://jsfiddle.net/nbh4r9u8/1/" class="hint">!!Testcase</a>.
-								<a href="https://jsfiddle.net/nbh4r9u8/2/" class="hint">!Testcase</a>.
-								<a href="https://jsfiddle.net/nbh4r9u8/3/" class="hint">!Testcase</a>.
-							</div>
+
+							ISSUE(467): Fixup collapsible whitespace
 
 					</ol>
 				</li>
@@ -899,22 +886,7 @@ spec:css21; type:property; text:max-width
 
 		</div>
 
-		<div class="issue">
-			<strong>This proposal does not respect these stated CSS 2.1 requirements:</strong><br/>
-			UAs must compute an initial left and right border width for the table
-				by examining the first and last cells in the first row of the table.
-			The left border width of the table is half of the first cell's collapsed left border,
-				and the right border width of the table is half of the last cell's collapsed right border.
-			If subsequent rows have larger collapsed left and right borders,
-				then any excess spills into the margin area of the table.
-		</div>
-
-		<div class="issue">
-			This proposal is doing worse than Edge and Firefox (but better than Chrome) when
-				row- or colspanned cells have border styles which conflict with their neighbors,
-				and those neighbors have different styles which conflict with each other.
-			This is a necessary trade-of to make the model sane.
-		</div>
+		ISSUE(604): border-collapsing breaking change from 2.1
 
 		<!--------------------------------------------------------------------------------->
 		<h4 id="conflict-resolution-for-collapsed-borders">Conflict Resolution for Collapsed Borders</h4>
@@ -1035,15 +1007,7 @@ spec:css21; type:property; text:max-width
 			set CurrentlyWinningBorderProperties to its properties&#8221;.
 		</div>
 
-		<div class="issue">
-			There is an outstanding proposal from Fantasai to 
-				change the "more specific than" part of these rules 
-				to "as specific or more than". 
-			This would change the priority order 
-				from
-					cell, track, track-group, table
-				to
-					table, track-group, track, cell.
+		ISSUE(606): harminozation of collapsed borders
 
 		</div>
 
@@ -1172,21 +1136,13 @@ spec:css21; type:property; text:max-width
 					<ul>
 						<li><a>In separated-borders mode</a>: the computed horizontal padding and border of the table-root
 						<li><a>In collapsed-borders mode</a>: the used border-width values of the cell (half the winning border-width)
-							<div class="issue">
-								Is this the correct way to account for the various changes 
-								that have gone into CSS2.1 
-								regarding which border sticks out into the margin?
-							</div>
 					</ul>
 
 					<p class="note">
 						The margins are not included in the table intrinsic offsets
 							because handling of margins depends on the 'caption-side' property.
-					<div class="issue">But doesn't that break handling of percentage padding?
-						<a class="hint" href="https://jsfiddle.net/j5dbco4m/">
-							I don't think so because they are resolved based on parent anyway
-						</a>
-					</div>
+
+					ISSUE(608): Handling of intrinsic offsets when in border collapsing mode
 
 				<!--------------------------------------------------------------------------------->
 				<dt><dfn>total horizontal border spacing</dfn></dt>