[css2] Removed dead comments, added a link, minor language fix.

ianbjacobs · ianbjacobs · commit 1c8ce107ea91 · 1998-04-28T22:26:16.000Z
--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%401549
diff --git a/css2/cascade.src b/css2/cascade.src
@@ -1,6 +1,6 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: cascade.src,v 2.25 1998-04-26 23:04:14 bbos Exp $ -->
+<!-- $Id: cascade.src,v 2.26 1998-04-28 22:26:16 ijacobs Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Assigning property values, Cascading, and Inheritance</TITLE>
@@ -29,8 +29,7 @@ on the following mechanisms (in order of precedence):</p>
 
 <ol>
 <li>If the <a href="#cascade">cascade</a> results in a value,
-use it. <!-- If the value is 'inherit', use the value of the parent
-element. -->
+use it.
 
 <li>Otherwise, if the property is <a
 href="#inheritance">inherited</a>, use the value of the parent
@@ -280,7 +279,6 @@ the same precedence rules apply.
 
 <H3><a name="cascading-order">Cascading order</a></H3>
 
-<!-- Removed concept of "algorithm" [12/4/1998,BB] -->
 <P>To find the value for an element/property combination, user agents
 must apply the following sorting order:</p>
 
@@ -289,8 +287,7 @@ must apply the following sorting order:</p>
       Find all declarations that apply to the element and property in
       question, for the target <a href="media.html">media type</a>.
       Declarations apply if the associated selector <A
-      HREF="selector.html">matches</A> the element in question. <!-- If no
-      declarations apply, terminate the algorithm. -->
+      HREF="selector.html">matches</A> the element in question.
 
     <LI>
       The primary sort of the declarations is by weight and origin:  for normal
@@ -304,33 +301,21 @@ must apply the following sorting order:</p>
       origin as the style sheet that imported it.
 
     <LI>
-      The secondary sort is by specificity of selector: more specific selectors will
-      override more general ones. <!-- The definition and calculation
-      of specificity depends on the document language (see below). [I
-      don't think so. BB]--> 
-      Pseudo-elements and pseudo-classes are counted as normal
-      elements and classes, respectively.
+      The secondary sort is by <a href="#specificity">specificity</a> 
+      of selector: more specific
+      selectors will override more general ones.  Pseudo-elements and
+      pseudo-classes are counted as normal elements and classes,
+      respectively.
 
     <LI> Finally, sort by order specified: if two rules have the same
     weight, origin and specificity,
     the latter specified wins. Rules in imported style sheets are
     considered to be before any rules in the style sheet itself.
 </OL>
 
-<!--
-<P>The search for the property value must be terminated when any of
-the above steps yields a rule that has a higher weight than the other
-rules that apply to the same element/property combination.
--->
-<!--
-<P>Note that "!important" may occur in author's and UA's style sheets,
-but only has an effect in the user's style sheets.
-[nope, Chris Wilson wanted it to count, HWL]
--->
-
 <P> Apart from the "!important" setting on individual declarations,
 this strategy gives author's style sheets higher weight than those of
-the reader. It is therefore important that the user agent gives the
+the reader. It is therefore important that the user agent give the
 user the ability to turn off the influence of a certain style sheet,
 e.g., through a pull-down menu.
 
