[cssom] Linkify some stuff in the serialization section.

And add an issue about <url> serialization, which is not right.

Author: emilio

cssom-1/Overview.bs

@@ -2578,13 +2578,13 @@ depends on the component, as follows:
  <dd>The keyword
  <a lt="ASCII lowercase">converted to ASCII lowercase</a>.
 
- <dt>&lt;angle>
+ <dt><<angle>>
  <dd>
   The &lt;number> component serialized as per &lt;number> followed by the unit in canonical form as defined in its respective specification.
 
   Issue: Probably should distinguish between specified and computed / resolved values.
 
- <dt>&lt;color>
+ <dt><<color>>
  <dd>
  If &lt;color&gt; is a component of a resolved or computed value, then
  return the color using the <code>rgb()</code> or <code>rgba()</code> functional
@@ -2620,7 +2620,7 @@ depends on the component, as follows:
 
  In the above rules, the string "<code>, </code>" denotes a COMMA (U+002C) followed by a single SPACE (U+0020).
 
- If &lt;color&gt; is a component of a specified value, then
+ If <<color>> is a component of a specified value, then
  return the color as follows:
  <ol>
  <li>If the color was explicitly specified by the author, then return the original, author specified color value.
@@ -2629,7 +2629,7 @@ depends on the component, as follows:
 
  Issue: Should author specified values be normalized for case? Or should original case be preserved?
 
- <dt>&lt;alphavalue>
+ <dt><<alphavalue>>
  <dd>
   If the value is internally represented as an integer between 0 and 255 inclusive (i.e. 8-bit unsigned integer),
   follow these steps:
@@ -2646,7 +2646,7 @@ depends on the component, as follows:
 
   Otherwise, return the result of serializing the given value as a &lt;number>.
 
- <dt>&lt;counter>
+ <dt><<counter>>
  <dd>
   The return value of the following algorithm:
   <ol>
@@ -2663,28 +2663,28 @@ depends on the component, as follows:
   </ol>
 
 
- <dt>&lt;frequency>
+ <dt><<frequency>>
  <dd>
   The &lt;number> component serialized as per &lt;number> followed by the unit in its canonical form as defined in its respective specification.
 
   Issue: Probably should distinguish between specified and computed / resolved values.
 
- <dt>&lt;identifier>
+ <dt><<identifier>>
  <dd>The identifier
  <a lt="serialize an identifier">serialized as an identifier</a>.
 
- <dt>&lt;integer>
+ <dt><<integer>>
  <dd>A base-ten integer using digits 0-9 (U+0030 to U+0039) in the
  shortest form possible, preceded by "<code>-</code>" (U+002D) if it is
  negative.
 
- <dt>&lt;length>
+ <dt><<length>>
  <dd>
   The &lt;number> component serialized as per &lt;number> followed by the unit in its canonical form as defined in its respective specification.
 
   Issue: Probably should distinguish between specified and computed / resolved values.
 
- <dt>&lt;number>
+ <dt><<number>>
  <dd>
   A base-ten number using digits 0-9 (U+0030 to U+0039) in the shortest form possible,
   using "<code>.</code>" to separate decimals (if any),
@@ -2693,20 +2693,20 @@ depends on the component, as follows:
 
   Note: scientific notation is not used.
 
- <dt>&lt;percentage>
+ <dt><<percentage>>
  <dd>The &lt;number> component serialized as per &lt;number> followed
  by the literal string "<code>%</code>" (U+0025).
 
- <dt>&lt;resolution>
+ <dt><<resolution>>
  <dd>The resolution in dots per <a lt=px value>CSS pixel</a> serialized as per
  &lt;number> followed by the literal string "<code>dppx</code>".
 
- <dt>&lt;ratio>
+ <dt><<ratio>>
  <dd>The numerator serialized as per &lt;number>
      followed by the literal string "<code> / </code>",
      followed by the denominator serialized as per &lt;number>.
 
- <dt>&lt;shape>
+ <dt><<shape>>
  <dd>
   The return value of the following algorithm:
   <ol>
@@ -2719,19 +2719,21 @@ depends on the component, as follows:
   </ol>
 
 
- <dt>&lt;string>
- <dt>&lt;family-name>
- <dt>&lt;specific-voice>
+ <dt><<string>>
+ <dt><<family-name>>
+ <dt><<specific-voice>>
  <dd>The string
  <a lt="serialize a string">serialized as a string</a>.
 
- <dt>&lt;time>
+ <dt><<time>>
  <dd>The time in seconds serialized as per &lt;number> followed by
  the literal string "<code>s</code>".
 
- <dt>&lt;uri>
+ <dt><<url>>
  <dd>The <a>absolute-URL string</a>
  <a lt="serialize a URL">serialized as URL</a>.
+
+ Issue: This should differentiate specified and computed <<url>> values, see <a href="https://github.com/w3c/csswg-drafts/issues/3195">#3195</a>.
 </dl>