machine-generated version

Author: howcome

css-gcpm/Overview.html

@@ -11,7 +11,7 @@
   <meta content="CSS Generated Content for Paged Media Module"
    name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2013-07-10 name=dcterms.date>
+  <meta content=2013-07-24 name=dcterms.date>
   <meta content="Håkon Wium Lie" name=dcterms.creator>
   <meta content=W3C name=dcterms.publisher>
   <meta content="http://dev.w3.org/csswg/css3-gcpm/" name=dcterms.identifier>
@@ -42,13 +42,13 @@
 
    <h1>CSS Generated Content for Paged Media Module</h1>
 
-   <h2 class="no-num no-toc" id=w3c-working>Editor's Draft 10 July 2013</h2>
+   <h2 class="no-num no-toc" id=w3c-working>Editor's Draft 24 July 2013</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://dev.w3.org/csswg/css3-gcpm/">http://www.w3.org/TR/2013/ED-css3-gcpm-20130710/</a>
+     href="http://dev.w3.org/csswg/css3-gcpm/">http://www.w3.org/TR/2013/ED-css3-gcpm-20130724/</a>
 
     <dt>Latest version:
 
@@ -1262,8 +1262,9 @@ <h2 id=footnotes><span class=secno>5. </span>Footnotes</h2>
 
    <li>one predefined counter: ‘<code class=css>footnote</code>’
 
-   <li>one new value on the ‘<code class=property>content</code>’
-    property: ‘<code class=css>target-pull()</code>’
+   <li class=unimplemented>one new value on the ‘<code
+    class=property>content</code>’ property: ‘<code
+    class=css>target-pull()</code>’
 
    <li>border segments
     <!--<li>two new 'list-style-type' values: ''super-decimal'', and symbol(...)-->
@@ -1292,7 +1293,7 @@ <h2 id=footnotes><span class=secno>5. </span>Footnotes</h2>
 </pre>
   </div>
 
-  <div class=example>
+  <div class="example unimplemented">
    <p>To support legacy browsers, it is often better to make a link to the
     note rather than including the text inline. This example shows how to
     fetch the content of a note and place it in a footnote.
@@ -1359,15 +1360,16 @@ <h3 id=turning-elements-into-footnotes><span class=secno>5.1.
   <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 ‘<code class=property>display</code>’ property on footnote
-   elements is ignored. Instead, the value of the ‘<code
-   class=property>display</code>’ property in the @footnote context
-   determines if footnotes are block or inline elements.
+  <div class=unimplemented>
+   <p>The ‘<code class=property>display</code>’ property on footnote
+    elements is ignored. Instead, the value of the ‘<code
+    class=property>display</code>’ 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:
+   <div class=example>
+    <p>In this example, the footnotes are displayed inline:
 
-   <pre>
+    <pre>
 @footnote {
   display: inline;
 }
@@ -1376,11 +1378,12 @@ <h3 id=turning-elements-into-footnotes><span class=secno>5.1.
 }
 </pre>
 
-   <p>Here is one possible presentation of inline footnotes:
+    <p>Here is one possible presentation of inline footnotes:
 
-   <pre>
+    <pre>
 ¹ The first footnote. º The second footnote.
 </pre>
+   </div>
   </div>
   <!--
 <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).