1. ms2ger
  2. Anolis

Commits

Geoffrey Sneddon  committed 0ab5ec3

Better define finding the W3C status.

  • Participants
  • Parent commits 2f902e3
  • Branches default

Comments (0)

Files changed (2)

File README.html

View file
  • Ignore whitespace
 
 <p>The <dfn id=w3c-status>W3C status</dfn> is found, when needed by one of the substitutions,
 by iterating all text nodes in document order (i.e., attribute values and
-comments have no effect), and for each node, the following is done:</p>
+comments have no effect), and for each node, the following is done (in this
+order):</p>
 
 <ol>
 	<li>If the node contains, case-insensitively, "latest version", searching
 stops, and the default is used (ED).
 	</li><li>Otherwise, if the node, case-sensitively, contains "http://www.w3.org/TR/"
 followed by one of "MO", "WD", "CR", "PR", "REC", "PER", or "NOTE", which in
-turn is followed by U+002D HYPHEN-MINUS (-), then the status is whatever matched
-the previous list of options.
+turn is followed by U+002D HYPHEN-MINUS (-), then searching stops, and the
+status is whatever matched the previous list of options by the first match in
+the text node.
 </li></ol>
 
+<p>A side-effect of doing it in this order is the fact that if a node contains
+both of these possible strings is that the latter is ignored, meaning that the
+default (ED) is used.</p>
+
 <!-- I wish the above was more sane — it took me several hours to work out
 (though the comment in the CSS3 Module Postprocessor docs saying, "If there is a
 H2 subheading under the H1 that gives the spec's status, the [STATUS] variable

File README.src.html

View file
  • Ignore whitespace
 
 <p>The <dfn>W3C status</dfn> is found, when needed by one of the substitutions,
 by iterating all text nodes in document order (i.e., attribute values and
-comments have no effect), and for each node, the following is done:</p>
+comments have no effect), and for each node, the following is done (in this
+order):</p>
 
 <ol>
 	<li>If the node contains, case-insensitively, "latest version", searching
 stops, and the default is used (ED).
 	<li>Otherwise, if the node, case-sensitively, contains "http://www.w3.org/TR/"
 followed by one of "MO", "WD", "CR", "PR", "REC", "PER", or "NOTE", which in
-turn is followed by U+002D HYPHEN-MINUS (-), then the status is whatever matched
-the previous list of options.
+turn is followed by U+002D HYPHEN-MINUS (-), then searching stops, and the
+status is whatever matched the previous list of options by the first match in
+the text node.
 </ol>
 
+<p>A side-effect of doing it in this order is the fact that if a node contains
+both of these possible strings is that the latter is ignored, meaning that the
+default (ED) is used.</p>
+
 <!-- I wish the above was more sane — it took me several hours to work out
 (though the comment in the CSS3 Module Postprocessor docs saying, "If there is a
 H2 subheading under the H1 that gives the spec's status, the [STATUS] variable