x

Author: howcom

css3-gcpm/Overview.html

@@ -492,24 +492,35 @@ <h4 id=setting-named-strings-the-string-set-pro><span class=secno>2.1.1.
      <dt>&lsquo;<code class=css>env()</code>&rsquo;
 
      <dd>This function returns data from the environment of the user at the
-      time of formatting.
-      <div class=example>
-       <p>Possible uses of this function are:
+      time of formatting. The function accepts one of these keywords:
+      <ul>
+       <li>env(url): returns the URL of the document
 
-       <pre>
-string-set: date env(date);
-string-set: date env(time);
-string-set: date env(date-time);
-string-set: url env(url);
-</pre>
-      </div>
+       <li>env(date): returns the date on the user's system at the time of
+        formatting
+
+       <li>env(time): returns the time on the user's system at the time of
+        formatting
+
+       <li>env(date-time): returns the date and time on the user's system at
+        the time of formatting
+      </ul>
 
       <p class=note>Information about date and time is formatted according to
        the locale of the user. Implementors can get access to preformatted
        strings by way of the <a
        href="http://www.opengroup.org/onlinepubs/009695399/functions/strftime.html">strftime</a>
        function. The date, time and date-time strings can be found by using
-       the "%x", "%X" and "%c" conversion strings, respectively
+       the "%x", "%X" and "%c" conversion strings, respectively.
+
+      <div class=example>
+       <pre>
+string-set: url env(url);
+string-set: date env(date);
+string-set: date env(time);
+string-set: date env(date-time);
+</pre>
+      </div>
     </dl>
   </dl>
   <!--<p class="issue">Should target-counter() and leader() also be allowed?</p>-->
@@ -1106,7 +1117,7 @@ <h2 id=footnotes><span class=secno>5. </span>Footnotes</h2>
 
    <pre>
 &lt;style>
-.footnote { float: footnote; display: block; }
+.footnote { float: footnote }
 &lt;/style>
 
 &lt;p>A sentence consists of words. &lt;span class="footnote">Most often.&lt;/span>.
@@ -1134,7 +1145,6 @@ <h2 id=footnotes><span class=secno>5. </span>Footnotes</h2>
 @media print {
   .footnote { 
     float: footnote;
-    display: block;
     content: target-pull(attr(href, url)) }
   .call { display: none }
 }
@@ -1168,7 +1178,6 @@ <h2 id=footnotes><span class=secno>5. </span>Footnotes</h2>
 span[title]::after { 
   content: attr(title);
   float: footnote;
-  display: block;
 }
 </pre>
   </div>
@@ -1185,21 +1194,27 @@ <h3 id=turning-elements-into-footnotes><span class=secno>5.1.
    <pre>
 span.footnote { 
   float: footnote;
-  display: block;
 }
 </pre>
   </div>
 
-  <p>The &lsquo;<code class=property>display</code>&rsquo; property
-   determines how elements in the footnote area are displayed.
+  <p>Footnote elements are presented inside the <em>footnote area</em>, but
+   they inherit through their normal place in the structure of the document.
+
+  <p>The &lsquo;<code class=property>display</code>&rsquo; property on
+   footnote elements is ignored. Instead, the value of the &lsquo;<code
+   class=property>display</code>&rsquo; property in the @footnote context
+   determines if footnotes are block or inline elements.
 
   <div class=example>
    <p>In this example, the footnotes are displayed inline:
 
    <pre>
+@footnote { 
+  display: inline;
+}
 span.footnote { 
   float: footnote;
-  display: inline; /* probably not necessary for &lt;span&gt; elements */
 }
 span.footnote::before { 
   content: counter(footnote);
@@ -1213,20 +1228,13 @@ <h3 id=turning-elements-into-footnotes><span class=secno>5.1.
 </pre>
   </div>
 
-  <p class=issue>Instead of relying on the &lsquo;<code
-   class=property>display</code>&rsquo; property for each footnote element,
-   there could be a setting in @footnote for this.
+  <p class=issue>Another way to achieve this would be to introduce different
+   keywords for inline and block footnotes (e.g., float: footnote-inline,
+   float: footnote-block).
 
   <p>For each new footnote element, the &lsquo;<code
    class=css>footnote</code>&rsquo; counter is automatically incremented.
 
-  <p>Footnote elements are presented inside the <em>footnote area</em>, but
-   they inherit through their normal place in the structure of the document.
-   <!--
-<p class="issue">There has been a number of proposals on how to achieve this, including &lsquo;<code class=css>position: footnote</code>&rsquo;, &lsquo;<code class=css>flow: footnote</code>&rsquo;, and &lsquo;<code class=css>display: footnote</code>&rsquo;. The current thinking is that &lsquo;<code class=property>float</code>&rsquo; is suitable as the content still takes up space.
--->
-   
-
   <h3 id=the-footnote-area><span class=secno>5.2. </span>The footnote area</h3>
 
   <p>All elements with &lsquo;<code class=css>float: footnote</code>&rsquo;