[css-values] Update <custom-ident> section to match current thinking on disambiguation, insofar as possible. Fix crosslinking.

--HG--
extra : rebase_source : fc884180d312589f2a0dbcfc76f89d8e2f9cda01

Author: fantasai

css-values/Overview.bs

@@ -68,7 +68,7 @@ Component value types</h3>
 
 	<ol>
 		<li>
-			<a href="#keywords">keyword</a> values (such as ''auto'', ''disc'', etc.),
+			<a href="#keywords">keyword</a> values (such as <css>auto</css>, ''disc'', etc.),
 			which appear literally, without quotes (e.g. <code>auto</code>)
 
 		<li>
@@ -307,7 +307,7 @@ Property value examples</h3>
 				    <td>''3''
 				<tr><td>'text-align'
 				    <td>left | right | center | justify
-				    <td>''center''
+				    <td>''text-align/center''
 				<tr><td>'padding-top'
 				    <td>&lt;length> | &lt;percentage>
 				    <td>''5%''
@@ -388,21 +388,21 @@ Author-defined Identifiers: the <<custom-ident>> type</h3>
 	The <a>CSS-wide keywords</a> are not valid <<custom-ident>>s.
 	The ''default'' keyword is reserved
 	and is also not a valid <<custom-ident>>.
+	Specifications using <<custom-ident>> must specify clearly
+	what other keywords are excluded from <<custom-ident>>, if any--
+	for example by saying that any pre-defined keywords in that property's value definition are excluded.
+	Excluded keywords are excluded in all <a title="ASCII case-insensitive">ASCII case permutations</a>.
 
-	Specifications using <<custom-ident>> should specify clearly
-	what other keywords are excluded from <<custom-ident>>&mdash;for
-	example by saying that any pre-defined keywords in that property's value definition are excluded.
-	As a general rule, an identifier that could be interpreted as a pre-defined keyword
-	in any position or multiplication of the <<custom-ident>> component value
-	is excluded,
-	and is invalid as a <<custom-ident>> matching to that component value
-	even in positions where its use would be technically unambiguous.
-	For example, if a keyword could be misparsed when specified
-	as the first item of a ''<<custom-ident>>+'' list,
-	it is invalid when specified in any position in that list.
-
-	Excluded keywords are excluded in all ASCII case permutations.
+	When parsing positionally-ambiguous keywords in a property value,
+	a <<custom-ident>> production can only claim the keyword if no other unfulfilled production can claim it.
 
+	<div class="example">
+		For example, the shorthand declaration ''animation: ease-in ease-out''
+		is equivalent to the longhand declarations 
+		''animation-timing-function: ease-in; animation-name: ease-out;''.
+		''ease-in'' is claimed by the <<single-timing-function>> production belonging to 'animation-timing-function',
+		leaving ''ease-out'' to be claimed by the <<custom-ident>> production belonging to 'animation-name'.
+	</div>
 
 <h3 id="strings">
 Quoted Strings: the <<string>> type</h3>
@@ -669,7 +669,7 @@ Relative lengths</h3>
 Font-relative lengths: the ''em'', ''ex'', ''ch'', ''rem'' units</h4>
 
 	Aside from ''rem'' (which refers to the font-size of the root element),
-	the <dfn export>font-relative lengths</dfn> refer to the font metrics of the element on which they are used.
+	the <dfn export id="font-relative length">font-relative lengths</dfn> refer to the font metrics of the element on which they are used.
 	The exception is when they occur in the value of the 'font-size' property itself,
 	in which case they refer to the computed font metrics of the parent element
 	(or the computed font metrics corresponding to the initial values of the 'font' property,
@@ -730,7 +730,7 @@ Viewport-percentage lengths: the ''vw'', ''vh'', ''vmin'', ''vmax'' units</h4>
 	<a href="http://www.w3.org/TR/CSS21/visudet.html#containing-block-details">initial containing block</a>.
 	When the height or width of the initial containing block is changed,
 	they are scaled accordingly.
-	However, when the value of 'overflow' on the root element is ''auto'',
+	However, when the value of 'overflow' on the root element is ''overflow/auto'',
 	any scroll bars are assumed not to exist.
 	<span class='note'>Note that the initial containing block's size is affected by the presence of scrollbars on the viewport.</span>
 
@@ -1012,7 +1012,7 @@ Images: the <<image>> type</h3>
 	The <<position>> data type is defined in [[!CSS3BG]].
 	UAs that support CSS Backgrounds &amp; Borders Level 3 or its successor must interpret <<position>> as defined therein.
 
-<h2 id="functional-notation">
+<h2 id="functional-notations">
 Functional Notations</h2>
 
 	A <dfn>functional notation</dfn> is a type of component value
@@ -1223,7 +1223,7 @@ Computed Value</h4>
 	e.g. ''calc(100% - 100% + 1em)'' resolves to ''calc(0% + 1em)'',
 	not to ''calc(1em)''.
 	If there are special rules for computing percentages in a value
-	(e.g. <a href="http://www.w3.org/TR/CSS21/visudet.html#the-height-property">the 'height' property</a>),
+	(e.g. <a href="http://www.w3.org/TR/CSS21/visudet.html#the-height-property">the <css>height</css> property</a>),
 	they apply whenever a ''calc()'' expression contains percentages.
 
 	Note: Thus, the computed value of a ''calc()'' expression can be represented
@@ -1260,7 +1260,7 @@ Computed Value</h4>
 	math expressions involving percentages for widths and heights on
 	table columns, table column groups, table rows, table row groups, and table cells
 	in both auto and fixed layout tables
-	MAY be treated as if ''auto'' had been specified.
+	MAY be treated as if ''width/auto'' had been specified.
 
 
 <h4 id='calc-range'>
@@ -1298,7 +1298,7 @@ Toggling Between Values: ''toggle()''</h3>
 	<div class='example'>
 		The following example cycles markers for nested lists,
 		so that a top level list has ''disc''-shaped markers,
-		but nested lists use ''circle'', then ''square'', then ''box'',
+		but nested lists use ''list-style-type/circle'', then ''square'', then ''box'',
 		and then repeat through the list of marker shapes,
 		starting again (for the 5th list deep) with ''disc''.
 
@@ -1354,7 +1354,7 @@ Toggling Between Values: ''toggle()''</h3>
 	not a particular serialization [[!CSS21]],
 	so comparison between computed values should always be unambiguous and have the expected result.
 	For example,
-	a Level 2 <a href="http://www.w3.org/TR/CSS21/colors.html#propdef-background-position">'background-position'</a> computed value
+	a Level 2 <a property spec=css21>background-position</a> computed value
 	is just two offsets, each represented as an absolute length or a percentage,
 	so the declarations ''background-position: top center'' and ''background-position: 50% 0%''
 	produce identical computed values.
@@ -1412,7 +1412,7 @@ Ian's proposal:
 	In CSS3, the ''attr()'' expression can return many different types.
 	The ''attr()'' expression cannot return everything,
 	for example it cannot do counters, named strings, quotes,
-	or keyword values such as ''auto'', ''nowrap'', or ''baseline''.
+	or keyword values such as <css>auto</css>, <css>nowrap</css>, or <css>baseline</css>.
 	This is intentional,
 	as the intent of the ''attr()'' expression is not to make it possible to describe a presentational language's formatting using CSS,
 	but to enable CSS to take semantic data into account.
@@ -1464,14 +1464,14 @@ Ian's proposal:
 		Note that the default value need not be of the type given,
 		if the attr() expression is the entire property value.
 		For instance, if the type required of the attribute by the author is ''px'',
-		the default could still be ''auto'',
+		the default could still be <css>auto</css>,
 		like in ''width: attr(size px, auto);''.
 
 		If the attr() is used alongside other values to form the full property value,
 		however, the default value must match the attr()&#39;s type.
 		For example, ''box-shadow: attr(size px, inset) 5px 10px blue;'' is invalid,
 		even though it would create a valid declaration if you substituted the attr() expression
-		with either a ''px'' length <em>or</em> the ''inset'' keyword.
+		with either a ''px'' length <em>or</em> the ''box-shadow/inset'' keyword.
 	</div>
 
 	If the specified attribute exists on the element,
@@ -1790,7 +1790,7 @@ Changes</h2>
     <li>Made undefined namespace prefixes in ''attr()'' invalidate the function.
     <li>Per <a href="http://lists.w3.org/Archives/Public/www-style/2013Jan/0616.html">WG resolution</a>,
         made <a href="#viewport-relative-lengths">viewport-percentage units</a> respect scrollbars on the viewport
-        unless 'overflow' is ''auto'' (in which case they ignore the presence of scrollbars).
+        unless 'overflow' is ''overflow/auto'' (in which case they ignore the presence of scrollbars).
     <li>Deferred exact definition of <a href="#viewport-relative-lengths">viewport-percentage units</a>
         in paged media to <a href="http://www.w3.org/TR/css3-page/">CSS Paged Media</a>.
     <li>Added back the <<custom-ident>> term as a convenience notation, so that other specs can refer to it.