You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: css-gcpm/Overview.src.html
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -900,7 +900,7 @@ <h2>Footnotes</h2>
900
900
<li>one new page area: ''@footnote''
901
901
<li>two new pseudo-elements: ''::footnote-call'' and ''::footnote-marker''
902
902
<li>one predefined counter: ''footnote''
903
-
<li>one new value on the 'content' property: ''target-pull()''
903
+
<liclass=unimplemented>one new value on the 'content' property: ''target-pull()''
904
904
<li>border segments
905
905
<!--<li>two new 'list-style-type' values: ''super-decimal'', and symbol(...)-->
906
906
</ul>
@@ -930,7 +930,7 @@ <h2>Footnotes</h2>
930
930
931
931
</div>
932
932
933
-
<divclass=example>
933
+
<divclass="example unimplemented">
934
934
935
935
<p>To support legacy browsers, it is often better to make a link to
936
936
the note rather than including the text inline. This example shows how
@@ -999,6 +999,7 @@ <h3>Turning elements into footnotes</h3>
999
999
but they inherit through their normal place in the structure of the
1000
1000
document.
1001
1001
1002
+
<divclass=unimplemented>
1002
1003
<p>The 'display' property on footnote elements is ignored. Instead,
1003
1004
the value of the 'display' property in the @footnote context
1004
1005
determines if footnotes are block or inline elements.
@@ -1022,6 +1023,7 @@ <h3>Turning elements into footnotes</h3>
1022
1023
</pre>
1023
1024
</div>
1024
1025
1026
+
</div>
1025
1027
<!--
1026
1028
<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).
0 commit comments