[css-syntax] Markup fixes.

--HG--
extra : rebase_source : 47b0b1ff9b6612f76a87728984614b200e2def42

Author: tabatkins

css-syntax/Overview.html

@@ -115,7 +115,12 @@ <h2 class="no-num no-toc no-ref" id=contents><span class=content>Table of conten
 Informal Syntax Description</a><li><a href=#the-anb-type><span class=secno>6.2</span>
 The <code>&lt;an+b&gt;</code> type</a></ul><li><a href=#rule-defs><span class=secno>7</span>
 Defining Grammars for Rules and Other Values</a><ul class=toc><li><a href=#declaration-rule-list><span class=secno>7.1</span>
-Defining Block Contents: the <var>&lt;declaration-list&gt;</var>, <var>&lt;rule-list&gt;</var>, and <var>&lt;stylesheet&gt;</var> productions</a></ul><li><a href=#css-stylesheets><span class=secno>8</span>CSS stylesheets</a><ul class=toc><li><a href=#style-rules><span class=secno>8.1</span>Style rules</a><li><a href=#charset-rules><span class=secno>8.2</span><span class=css data-autolink=maybe>@charset</span> rules</a><li><a href=#other-at-rules-rules><span class=secno>8.3</span>Other at-rules rules</a></ul><li><a href=#serialization><span class=secno>9</span>Serialization</a><ul class=toc><li><a href=#serializing-anb><span class=secno>9.1</span>
+Defining Block Contents: the <span class=production data-autolink=link><var>&lt;declaration-list&gt;</var></span>, <span class=production data-autolink=link><var>&lt;rule-list&gt;</var></span>, and <span class=production data-autolink=link><var>&lt;stylesheet&gt;</var></span> productions</a></ul><li><a href=#css-stylesheets><span class=secno>8</span>
+CSS stylesheets</a><ul class=toc><li><a href=#style-rules><span class=secno>8.1</span>
+Style rules</a><li><a href=#charset-rules><span class=secno>8.2</span>
+<span class=css data-autolink=maybe>@charset</span> rules</a><li><a href=#other-at-rules-rules><span class=secno>8.3</span>
+Other at-rules rules</a></ul><li><a href=#serialization><span class=secno>9</span>
+Serialization</a><ul class=toc><li><a href=#serializing-anb><span class=secno>9.1</span>
 Serializing <var>&lt;an+b&gt;</var></a></ul><li><a href=#changes><span class=secno>10</span>Changes from CSS 2.1 and Selectors Level 3</a><li><a href=#acknowledgments><span class=secno></span>
 Acknowledgments</a><li><a href=#conformance><span class=secno></span>
 Conformance</a><ul class=toc><li><a href=#conventions><span class=secno></span>
@@ -2584,7 +2589,7 @@ <h2 data-level=7 id=rule-defs><span class=secno>7 </span><span class=content>
 	<div class=example>
 		For example, the syntax of the <span class=css data-autolink=maybe>translateX()</span> function is:
 
-<pre>translateX( &lt;translation-value&gt; )</pre>
+<pre>translateX( <a class=production data-autolink=link><var>&lt;translation-value&gt;</var></a> )</pre>
 <p>		However, the stylesheet may end with the function unclosed, like:
 
 <pre>.foo { transform: translate(50px</pre>
@@ -2598,23 +2603,23 @@ <h2 data-level=7 id=rule-defs><span class=secno>7 </span><span class=content>
 	</div>
 
 <h3 data-level=7.1 id=declaration-rule-list><span class=secno>7.1 </span><span class=content>
-Defining Block Contents: the <var>&lt;declaration-list&gt;</var>, <var>&lt;rule-list&gt;</var>, and <var>&lt;stylesheet&gt;</var> productions</span><a class=section-link href=#declaration-rule-list>§</a></h3>
+Defining Block Contents: the <a class=production data-autolink=link href=#declaration-list><var>&lt;declaration-list&gt;</var></a>, <a class=production data-autolink=link href=#rule-list><var>&lt;rule-list&gt;</var></a>, and <a class=production data-autolink=link href=#stylesheet><var>&lt;stylesheet&gt;</var></a> productions</span><a class=section-link href=#declaration-rule-list>§</a></h3>
 
 <p>	The CSS parser is agnostic as to the contents of blocks,
 	such as those that come at the end of some at-rules.
 	Defining the generic grammar of the blocks in terms of tokens is non-trivial,
 	but there are dedicated and unambiguous algorithms defined for parsing this.
 
-<p>	The <dfn data-dfn-type=production id=declaration-list><var>&lt;declaration-list&gt;</var></dfn> production represents a list of declarations.
+<p>	The <dfn data-dfn-type=production id=declaration-list>&lt;declaration-list&gt;</dfn> production represents a list of declarations.
 	It may only be used in grammars as the sole value in a block,
 	and represents that the contents of the block must be parsed using the <a href=#consume-a-list-of-declarations0>consume a list of declarations</a> algorithm.
 
-<p>	Similarly, the <dfn data-dfn-type=production id=rule-list><var>&lt;rule-list&gt;</var></dfn> production represents a list of rules,
+<p>	Similarly, the <dfn data-dfn-type=production id=rule-list>&lt;rule-list&gt;</dfn> production represents a list of rules,
 	and may only be used in grammars as the sole value in a block.
 	It represents that the contents of the block must be parsed using the <a href=#consume-a-list-of-rules0>consume a list of rules</a> algorithm.
 
-<p>	Finally, the <dfn data-dfn-type=production id=stylesheet><var>&lt;stylesheet&gt;</var></dfn> production represents a list of rules.
-	It is identical to <var>&lt;rule-list&gt;</var>,
+<p>	Finally, the <dfn data-dfn-type=production id=stylesheet>&lt;stylesheet&gt;</dfn> production represents a list of rules.
+	It is identical to <a class=production data-autolink=link href=#rule-list><var>&lt;rule-list&gt;</var></a>,
 	except that blocks using it default to accepting all rules
 	that aren't otherwise limited to a particular context.
 
@@ -2623,24 +2628,24 @@ <h3 data-level=7.1 id=declaration-rule-list><span class=secno>7.1 </span><span c
 		and to contain a list of declarations.
 		This is expressed with the following grammar:
 
-<pre>@font-face { &lt;declaration-list&gt; }</pre>
+<pre>@font-face { <a class=production data-autolink=link href=#declaration-list><var>&lt;declaration-list&gt;</var></a> }</pre>
 <p>		This is a complete and sufficient definition of the rule's grammar.
 
 <p>		For another example,
 		<span class=css data-autolink=maybe>@keyframes</span> rules are more complex,
 		interpreting their prelude as a name and containing keyframes rules in their block
 		Their grammar is:
 
-<pre>@keyframes &lt;keyframes-name&gt; { &lt;rule-list&gt; }</pre>	</div>
+<pre>@keyframes <a class=production data-autolink=link><var>&lt;keyframes-name&gt;</var></a> { <a class=production data-autolink=link href=#rule-list><var>&lt;rule-list&gt;</var></a> }</pre>	</div>
 
-<p>	For rules that use <var>&lt;declaration-list&gt;</var>,
+<p>	For rules that use <a class=production data-autolink=link href=#declaration-list><var>&lt;declaration-list&gt;</var></a>,
 	the spec for the rule must define which properties, descriptors, and/or at-rules are valid inside the rule;
 	this may be as simple as saying "The @foo rule accepts the properties/descriptors defined in this specification/section.",
 	and extension specs may simply say "The @foo rule additionally accepts the following properties/descriptors.".
 	Any declarations or at-rules found inside the block that are not defined as valid
 	must be removed from the rule's value.
 
-<p>	Within a <var>&lt;declaration-list&gt;</var>,
+<p>	Within a <a class=production data-autolink=link href=#declaration-list><var>&lt;declaration-list&gt;</var></a>,
 	<code>!important</code> is automatically invalid on any descriptors.
 	If the rule accepts properties,
 	the spec for the rule must define whether the properties interact with the cascade,
@@ -2655,25 +2660,25 @@ <h3 data-level=7.1 id=declaration-rule-list><span class=secno>7.1 </span><span c
 		define that the allowed declarations are the descriptors defined in the Fonts spec.
 	</div>
 
-<p>	For rules that use <var>&lt;rule-list&gt;</var>,
+<p>	For rules that use <a class=production data-autolink=link href=#rule-list><var>&lt;rule-list&gt;</var></a>,
 	the spec for the rule must define what types of rules are valid inside the rule,
-	same as <var>&lt;declaration-list&gt;</var>,
+	same as <a class=production data-autolink=link href=#declaration-list><var>&lt;declaration-list&gt;</var></a>,
 	and unrecognized rules must similarly be removed from the rule's value.
 
 	<div class=example>
 		For example, the grammar for <span class=css data-autolink=maybe>@keyframes</span> in the previous example must,
 		in addition to what is written there,
-		define that the only allowed rules are <var>&lt;keyframe-rule&gt;</var>s,
+		define that the only allowed rules are <a class=production data-autolink=link><var>&lt;keyframe-rule&gt;</var></a>s,
 		which are defined as:
 
-<pre>&lt;keyframe-rule&gt; = &lt;keyframe-selector&gt; { &lt;declaration-list&gt; }</pre>
+<pre><a class=production data-autolink=link><var>&lt;keyframe-rule&gt;</var></a> = <a class=production data-autolink=link><var>&lt;keyframe-selector&gt;</var></a> { <a class=production data-autolink=link href=#declaration-list><var>&lt;declaration-list&gt;</var></a> }</pre>
 <p>		Keyframe rules, then,
 		must further define that they accept as declarations all animatable CSS properties,
 		plus the <a class=property data-autolink=property title=animation-timing-function>animation-timing-function</a> property,
 		but that they do not interact with the cascade.
 	</div>
 
-<p>	For rules that use <var>&lt;stylesheet&gt;</var>,
+<p>	For rules that use <a class=production data-autolink=link href=#stylesheet><var>&lt;stylesheet&gt;</var></a>,
 	all rules are allowed by default,
 	but the spec for the rule may define what types of rules are <em>invalid</em> inside the rule.
 
@@ -2682,24 +2687,26 @@ <h3 data-level=7.1 id=declaration-rule-list><span class=secno>7.1 </span><span c
 		except more <span class=css data-autolink=maybe>@media</span> rules.
 		As such, its grammar is:
 
-<pre>@media &lt;media-query-list&gt; { &lt;stylesheet&gt; }</pre>
-<p>		It additionally defines a restriction that the <var>&lt;stylesheet&gt;</var> can not contain <span class=css data-autolink=maybe>@media</span> rules,
+<pre>@media <a class=production data-autolink=link><var>&lt;media-query-list&gt;</var></a> { <a class=production data-autolink=link href=#stylesheet><var>&lt;stylesheet&gt;</var></a> }</pre>
+<p>		It additionally defines a restriction that the <a class=production data-autolink=link href=#stylesheet><var>&lt;stylesheet&gt;</var></a> can not contain <span class=css data-autolink=maybe>@media</span> rules,
 		which causes them to be dropped from the outer rule's value if they appear.
 	</div>
 
 
-<h2 data-level=8 id=css-stylesheets><span class=secno>8 </span><span class=content>CSS stylesheets</span><a class=section-link href=#css-stylesheets>§</a></h2>
+<h2 data-level=8 id=css-stylesheets><span class=secno>8 </span><span class=content>
+CSS stylesheets</span><a class=section-link href=#css-stylesheets>§</a></h2>
 
 <p>	A CSS stylesheet is parsed with <a href=#parse-a-stylesheet0>Parse a stylesheet</a>,
 	interpreting the resulting <a href=#qualified-rule>qualified rules</a> and <a href=#at-rule>at-rules</a> as follows.
 	Each of these is either transformed into a <a href=#style-rules0>style rule</a> or another type of rule,
 	or is found invalid. Invalid rules are ignored with a <a href=#parse-errors>parse errors</a>.
 
 
-<h3 data-level=8.1 id=style-rules><span class=secno>8.1 </span><span class=content>Style rules</span><a class=section-link href=#style-rules>§</a></h3>
+<h3 data-level=8.1 id=style-rules><span class=secno>8.1 </span><span class=content>
+Style rules</span><a class=section-link href=#style-rules>§</a></h3>
 
 	<p>
-		<dfn data-dfn-type=link id=style-rules0 title="style rule|style rules">Style rules</dfn> are <a href=#qualified-rule>qualified rules</a>
+		<dfn data-dfn-type=link id=style-rules0 title="style rule">Style rules</dfn> are <a href=#qualified-rule>qualified rules</a>
 		that associate a <a href=http://dev.w3.org/csswg/selectors4/#selector-list>selector list</a> <a data-autolink=biblio data-biblio-type=normative href=#select title=SELECT>[SELECT]</a>
 		with a list of property declarations.
 		They are also called
@@ -2735,7 +2742,8 @@ <h3 data-level=8.1 id=style-rules><span class=secno>8.1 </span><span class=conte
 		but not they’re not inside <span class=css data-autolink=maybe>@keyframes</span> rules <a data-autolink=biblio data-biblio-type=informative href=#css3-animations title=CSS3-ANIMATIONS>[CSS3-ANIMATIONS]</a>.
 
 
-<h3 data-level=8.2 id=charset-rules><span class=secno>8.2 </span><span class=content><span class=css data-autolink=maybe>@charset</span> rules</span><a class=section-link href=#charset-rules>§</a></h3>
+<h3 data-level=8.2 id=charset-rules><span class=secno>8.2 </span><span class=content>
+<span class=css data-autolink=maybe>@charset</span> rules</span><a class=section-link href=#charset-rules>§</a></h3>
 
 	<p>
 		<dfn data-dfn-type=at-rule id=charset-rules0><span class=css data-autolink=maybe>@charset</span> rules</dfn> are <a href=#at-rule>at-rules</a> whose name is an <a href=#ascii-case-insensitive>ASCII case-insensitive</a> match for "charset".
@@ -2774,7 +2782,8 @@ <h3 data-level=8.2 id=charset-rules><span class=secno>8.2 </span><span class=con
 		of a stylesheet parse from bytes,
 		but they don’t have any other effect.
 
-<h3 data-level=8.3 id=other-at-rules-rules><span class=secno>8.3 </span><span class=content>Other at-rules rules</span><a class=section-link href=#other-at-rules-rules>§</a></h3>
+<h3 data-level=8.3 id=other-at-rules-rules><span class=secno>8.3 </span><span class=content>
+Other at-rules rules</span><a class=section-link href=#other-at-rules-rules>§</a></h3>
 
 	<p>
 		Other specifications may define specific types of at-rules based on their name.
@@ -2789,7 +2798,8 @@ <h3 data-level=8.3 id=other-at-rules-rules><span class=secno>8.3 </span><span cl
 		Margin rules <a data-autolink=biblio data-biblio-type=informative href=#css3page title=CSS3PAGE>[CSS3PAGE]</a> must be directly inside a <span class=css data-autolink=maybe>@page</span> rule.
 
 
-<h2 data-level=9 id=serialization><span class=secno>9 </span><span class=content>Serialization</span><a class=section-link href=#serialization>§</a></h2>
+<h2 data-level=9 id=serialization><span class=secno>9 </span><span class=content>
+Serialization</span><a class=section-link href=#serialization>§</a></h2>
 
 <p>	This specification does not define how to serialize CSS in general,
 	leaving that task to the CSSOM and individual feature specifications.
@@ -3240,7 +3250,6 @@ <h2 class="no-num no-ref" id=index><span class=content>
 <li>start with an identifier, <a href=#check-if-three-characters-would-start-an-identifier0 title="section 4.3.9">4.3.9</a>
 <li>start with a number, <a href=#check-if-three-characters-would-start-a-number0 title="section 4.3.10">4.3.10</a>
 <li>style rule, <a href=#style-rules0 title="section 8.1">8.1</a>
-<li>style rules, <a href=#style-rules0 title="section 8.1">8.1</a>
 <li>&lt;stylesheet&gt;, <a href=#stylesheet title="section 7.1">7.1</a>
 <li>top-level flag, <a href=#top-level-flag title="section 5.4.1">5.4.1</a>
 <li>uppercase letter, <a href=#uppercase-letter title="section 4.2">4.2</a>