W3C home > Mailing lists > Public > www-style@w3.org > June 2006

Re: [css3-gcpm] New WD: Generated Content for Paged Media

From: Kelly Miller <lightsolphoenix@gmail.com>
Date: Thu, 15 Jun 2006 00:57:52 -0400
Message-ID: <4490E8D0.2060505@gmail.com>
To: bert@w3.org
CC: www-style@w3.org

Hash: SHA1

Some of my comments:

- - There should be a more specific description of how to get to the text.
For example, should all white space be preserved?

I imagine this would be best done with another property related to the
strings.  There are situations where both options would be useful.

- - However, if the leaders contains any non-white-space characters, white
space characters at the beginning and end of a leader must be removed.

If this is so, then leader(dotted) would not be equivalent to leader(".
"), because the latter's space would be collapsed.  So I suspect
preserving whitespace would be a better option.

- - The 'leader()' value accepts an optional second argument to determine
from which element property values are borrowed from. The argument can
be one of these:

    * 'current': Property values are borrowed from the (pseudo-)element
where the 'leader()' value is used. This is the default value.
    * 'root': Property values are borrowed from the root element.

Is there a better element to use than the root element? Perhaps the
initial value of the various properties?

There was a discussion about adding some sort of naming system to
elements.  Maybe use that here?  Also, I'd suggest allowing some sort of
id() function, for targetting styles of elements with certain id's.

- - There has been a number of proposals for these names. Instead of the
'position' property, these properties have been proposed: 'flow',
'float', 'display'.

In this case, I believe position is the right option.  Setting something
as a footnote IS changing its position in the document, after all.

- - Should there also be a footnote border style to achieve that solid
line that partially extends across the top from the left?

That's the first question that popped into my head after reading that
section.  I dunno if using a specific property for that is a fantastic
idea, though; more properties = more complex spec...

- - The reason for having a predefined "footnote" counter is to avoid
having to set "counter-increment: footnote" every time one sets
"position: footnote". However, is this a good enough reason?

In any situation in which counting is expected, I believe there should
be an automatic counter built in, and an implied counter-increment.
It'd really suck to have to add counter-increment(whatever) to every
single position: footnote; and besides, how would that be done in CSS as
it is?  It's not like you can style based on already set propeties.
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

Received on Thursday, 15 June 2006 04:58:07 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:24 UTC