remove <position> parsing in favor of upcoming css-values changes

Author: astearns

css-shapes-1/Overview.bs

@@ -536,18 +536,8 @@ Serialization of Basic Shapes</h3>
 	joining space-separated tokens with a single space,
 	and following each serialized comma with a single space.
 
-	The <<position>> values
-	(including the defaults)
-	in ''ellipse()'' and ''circle()''
-	serialize to their 2- and 4-value forms only,
-	preferring the 2-value form
-	when it can be expressed without calc(),
-	preferring left and top origins,
-	and preferring 0% over a zero length.
-
 <div class="example">
 
-
 	Since <<position>> keywords stand in for percentages, keywords without an offset turn into percentages.
 
 	<pre><code>

css-shapes-1/issues-cr-20141015.txt

@@ -52,18 +52,18 @@ Response: https://github.com/w3c/csswg-drafts/issues/3872#issuecomment-488498771
 Closed:   Rejected
 ----
 Issue 8.
-Summary:  
-From:     
-Comment:  
-Response: 
-Closed:   
+Summary:  [css-shapes] Consider ways to make the CORS limitation in CSS Shapes easier for authors 
+From:     Jen Simmons
+Comment:  https://github.com/w3c/csswg-drafts/issues/1481
+Response: https://github.com/w3c/csswg-drafts/issues/1481#issuecomment-542868955
+Closed:   Rejected
 ----
 Issue 9.
-Summary:  
-From:     
-Comment:  
-Response: 
-Closed:   
+Summary:  [css-shapes] Why does this spec need to special-case serialization of <position>?
+From:     Emilio Cobos Álvarez
+Comment:  https://github.com/w3c/csswg-drafts/issues/2301
+Response: https://github.com/w3c/csswg-drafts/issues/2301#issuecomment-418583325
+Closed:   Accepted
 ----
 Issue 10.
 Summary: