Re: [CSS3-GCPM] Three questions regarding footnotes

2009/3/17 Giovanni Campagna <>:
> 2009/3/17 thomas <>:
>> 1) It does not seem possible to have two footnote areas at the bottom
>> of the page (in the example, one for alphabetic footnotes, one for
>> numbered footnotes).
> Actually you may, just you need some more work (you need two elements,
> floated to footnote area, each one receiving data from named flows). A
> better solution would be
> @footnote <ident> {
> }
> float: footnote(<ident>);
> (or move-to: or position: or position-flow:)

I missed the possibility of having multiple named footnote areas.  The
draft mention always "*the* footnote area".  By the way, how do you
specify which footnote area is above the other one?  The draft states
that "If figures and footnotes [with 'float:bottom page]' are on the
same page, the footnotes will appear below the figures as they are
floated to the bottom before the figures."  But is there any rule
regarding multiple footnote areas?

>> 2) It does not seem possible to put several footnote references in a
>> single paragraph (as it is the case, in the example, for the
>> alphabetic footnote references).
> Why not? You just need to display:inline the appropriate ::footnote
> pseudo-element

Which "::footnote pseudo-element"?  The draft mentions only
"::footnote-call" and "::footnote-marker" (in this version: ).  Moreover, this is not that
simple, because you certainly want something to separate the
footnotes, i.e. an em dash:
[1] foo — [2] bar — [3] — baz

>> 3) The footnote #6 contains two div elements (two paragraphs). But is
>> it possible to put divs in a footnote? Certainly, something like this
>> is wrong:
>> <p>A sentence consists of <em>words. <div
>> class="footnote"><p>Most</p><p>often.</p></div></em></span>.
>> Should one close the em tag before the footnote-div and reopen it
>> afterwards? This would not be clean code.
> I agree that it is definitely not clean code, but it is specified and
> understandable, once you know the model.
> First the computed values for all properties are found, then elements
> in the CSS dom are laid out and rendered as if they were child of the
> element, pseudo-element, page area estabilishing the named flow
> (@footnote in this case).
> This means that first <div> gets font-style:inherit, computed to
> font-style:italic, then it is moved in the @footnote area, leaving
> <p>A sentence consists of <em>words. </em></p> (</span> is not
> correct, I assume a typo).

It was indeed a typo.  Thanks for the explanation.


Received on Tuesday, 17 March 2009 16:39:25 UTC