Skip to content

Commit ba22a4a

Browse files
author
howcome
committed
adding info on unimplemented parts of footnotes
1 parent e5085fa commit ba22a4a

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

css-gcpm/Overview.src.html

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -900,7 +900,7 @@ <h2>Footnotes</h2>
900900
<li>one new page area: ''@footnote''
901901
<li>two new pseudo-elements: ''::footnote-call'' and ''::footnote-marker''
902902
<li>one predefined counter: ''footnote''
903-
<li>one new value on the 'content' property: ''target-pull()''
903+
<li class=unimplemented>one new value on the 'content' property: ''target-pull()''
904904
<li>border segments
905905
<!--<li>two new 'list-style-type' values: ''super-decimal'', and symbol(...)-->
906906
</ul>
@@ -930,7 +930,7 @@ <h2>Footnotes</h2>
930930

931931
</div>
932932

933-
<div class=example>
933+
<div class="example unimplemented">
934934

935935
<p>To support legacy browsers, it is often better to make a link to
936936
the note rather than including the text inline. This example shows how
@@ -999,6 +999,7 @@ <h3>Turning elements into footnotes</h3>
999999
but they inherit through their normal place in the structure of the
10001000
document.
10011001

1002+
<div class=unimplemented>
10021003
<p>The 'display' property on footnote elements is ignored. Instead,
10031004
the value of the 'display' property in the @footnote context
10041005
determines if footnotes are block or inline elements.
@@ -1022,6 +1023,7 @@ <h3>Turning elements into footnotes</h3>
10221023
</pre>
10231024
</div>
10241025

1026+
</div>
10251027
<!--
10261028
<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).
10271029
-->

0 commit comments

Comments
 (0)