[css-content] placated bikeshed (for now)

Author: dauwhe

css-content/Overview.bs

@@ -13,7 +13,8 @@ Former Editor: Håkon Wium Lie, Opera Software, howcome@opera.com
 Former Editor: Ian Hickson, Google, ian@hixie.ch
 Ignored Terms: 
 Abstract: This CSS3 Module describes how to insert content in a document.
-Link Defaults: css21 (type) <uri>
+Link Defaults: css21 (type) <uri>, css-display-3 (value) inline
+Warning: Not Ready
 </pre>
 
 
@@ -154,9 +155,9 @@ h1 { content: url(header/mng), url(header/png), none; }
 </div>
 
 
-:: In the example above, if <code>header/mng</code> wasn't in a supported format, then <code>header/png</code> would have been used instead. In the example above, if <code>header/png</code> wasn't available either, then the <code>&lt;h1&gt;</code> element would be empty, as the last alternative is ''none''.</p>
+:: In the example above, if <code>header/mng</code> wasn't in a supported format, then <code>header/png</code> would have been used instead. In the example above, if <code>header/png</code> wasn't available either, then the <code>&lt;h1&gt;</code> element would be empty, as the last alternative is ''content/none''.</p>
 
-:: To make an element fallback on its contents, you have to explicitly give ''contents'' as a fallback:
+:: To make an element fallback on its contents, you have to explicitly give ''content/contents'' as a fallback:
 
 :: <div class="example">
 <pre>content: url(1), url(2), url(3), contents;</pre>
@@ -165,7 +166,7 @@ h1 { content: url(header/mng), url(header/png), none; }
 
 :: <p class="issue">What happens when no formats are supported, and the author does not explicitly indicate a fallback?</p>
 
-:: <p class="issue">Why doesn't an element fallback to ''contents'' unless an author explicitly says so?</p>
+:: <p class="issue">Why doesn't an element fallback to ''content/contents'' unless an author explicitly says so?</p>
 
 
 
@@ -185,7 +186,7 @@ h1 { content: url(header/mng), url(header/png), none; }
 
 : <dfn title="'content-property'!!'normal'">normal</dfn>
 
-:: For an element, this computes to ''contents''.</p>
+:: For an element, this computes to ''content/contents''.</p>
 
 :: For ''::before'' and ''::after'', this computes to ''inhibit''.
 
@@ -204,7 +205,7 @@ h1 { content: url(header/mng), url(header/png), none; }
 
 :: On elements, this inhibits the children of the element from being rendered as children of this element, as if the element was empty.
 
-:: On pseudo-elements, this inhibits the creation of the pseudo-element, as if 'display' computed to ''none''.
+:: On pseudo-elements, this inhibits the creation of the pseudo-element, as if 'display' computed to ''display/none''.
 
 :: In both cases, this further inhibits the creation of any pseudo-elements which have this pseudo-element as a superior.
 
@@ -224,7 +225,7 @@ h1 { content: url(header/mng), url(header/png), none; }
 
 :: :: If the value is the empty string, and the element or pseudo-element's 'display' property computes to anything but ''inline'', then the element or pseude-element contains an empty anonymous inline box, otherwise the element contains an empty string.
 
-:: :: (This is a formal way of saying that an empty string is different from ''none'' in that it forces the creation of a line box, even if the line box would be empty.)
+:: :: (This is a formal way of saying that an empty string is different from ''content/none'' in that it forces the creation of a line box, even if the line box would be empty.)
 
 
 
@@ -237,7 +238,7 @@ h1 { content: url(header/mng), url(header/png), none; }
 
 :: :: : If set on the element:
 
-:: :: :: Always honoured. Note that this is the default, since the initial value of 'content' is ''normal'' and ''normal'' computes to ''contents'' on an element.
+:: :: :: Always honoured. Note that this is the default, since the initial value of 'content' is ''content/normal'' and ''content/normal'' computes to ''content/contents'' on an element.
 
 :: :: : If set on one of the element's other pseudo-elements:
 
@@ -248,7 +249,7 @@ h1 { content: url(header/mng), url(header/png), none; }
          3. ::after
 
 
-:: :: :: If it is already used, then it evaluates to nothing (like ''none''). Only pseudo-elements that are actually generated are checked. 
+:: :: :: If it is already used, then it evaluates to nothing (like ''content/none''). Only pseudo-elements that are actually generated are checked. 
 
 :: :: :: In the following case:
 :: :: :: <div class="example">
@@ -257,7 +258,7 @@ foo::after { content: contents; }
 </pre>
 </div>
 
-:: :: :: ...the element's 'content' property would compute to ''contents'' and the after pseudo element would have no contents (equivalent to ''none'') and thus would not appear. 
+:: :: :: ...the element's 'content' property would compute to ''content/contents'' and the after pseudo element would have no contents (equivalent to ''content/none'') and thus would not appear. 
 
 :: :: :: <div class="example">
 <pre>foo { content: none; } 
@@ -271,7 +272,7 @@ foo::after { content: contents; }
 :: :: :: <p class="issue">Use cases for suppressing the content on the element and using it in a pseudo-element would be welcome.</p>
 
 
-:: :: :: Note that while it is useless to include ''contents'' twice in a single 'content' property, that is not a parse error. The second occurrence simply has no effect, as it has already been used. It is also not a parse error to use it on a marker pseudo-element, it is only during the rendering stage that it gets treated like ''none''.
+:: :: :: Note that while it is useless to include ''content/contents'' twice in a single 'content' property, that is not a parse error. The second occurrence simply has no effect, as it has already been used. It is also not a parse error to use it on a marker pseudo-element, it is only during the rendering stage that it gets treated like ''content/none''.
 
 
 :: : 'counter()' and 'counters()'
@@ -290,7 +291,7 @@ foo::after { content: contents; }
 
 :: : ''no-open-quote'' and ''no-close-quote''
 
-:: :: Inserts nothing (as in ''none''), but increments (decrements) the level of nesting for quotes. See the section on <a href="#specifying-quotes">quotes</a> for more information.
+:: :: Inserts nothing (as in ''content/none''), but increments (decrements) the level of nesting for quotes. See the section on <a href="#specifying-quotes">quotes</a> for more information.
 
 
 :: : &lt;datetime&gt;
@@ -390,7 +391,7 @@ HTML has long had the <code>q</code> element, used to delimit quotations. The ''
     Media: all
 </pre>
 
-<p class="issue">The previous ED had an initial value of ''text'', which was an error. [[CSS21]] has initial value of "depends on user agent". Do we use ''auto'' for things like this, or is it just a UA stylesheet issue?</p>
+<p class="issue">The previous ED had an initial value of ''text'', which was an error. [[CSS21]] has initial value of "depends on user agent". Do we use <code>auto</code> for things like this, or is it just a UA stylesheet issue?</p>
 
 
 <p>This property specifies quotation marks for any number of embedded quotations. Values have the following meanings:</p>
@@ -1057,7 +1058,7 @@ A bookmark references a point in the document, which we define to the be  the in
 bookmark-level
 </h3>
 
-The 'bookmark-level' property determines if a bookmark is created, and at what level. If this property is absent, or has value ''none'', no bookmark should be generated, regardless of the values of 'bookmark-label' or 'bookmark-state'.
+The 'bookmark-level' property determines if a bookmark is created, and at what level. If this property is absent, or has value ''bookmark-level/none'', no bookmark should be generated, regardless of the values of 'bookmark-label' or 'bookmark-state'.
 
 <pre class="propdef">
 Name: <dfn>bookmark-level</dfn>
@@ -1161,7 +1162,7 @@ Computed value: specified value
 
 <h2 id="changes">Changes since the 14 May 2003 Working Draft</h2>
 
-* Terminology section deleted, as that information is now in [[css-pseudo-4]]
+* Terminology section deleted, as that information is now in [[CSS-PSEUDO-4]]
 
 * Pseudo-elements section replaced by [[CSS-PSEUDO-4]]