W3C home > Mailing lists > Public > www-style@w3.org > May 2007

[css3-gcpm] Comments

From: Michael Day <mikeday@yeslogic.com>
Date: Mon, 07 May 2007 21:47:31 +1000
Message-ID: <463F11D3.2010709@yeslogic.com>
To: www-style@w3.org

> http://www.w3.org/TR/2007/WD-css3-gcpm-20070504


  - string-set introduces some new keywords: self, before, after,
first-letter. Currently, Prince accepts anything that the content
property would accept as an argument to string-set. This includes things
that the spec doesn't allow, such as target-counter() and leader().

  - In some ways, it seems better to introduce a first-letter() function
than to add first-letter keywords to everything else. CSS doesn't
usually do things this way, though.

  - Prince does not support last-except on the string() function.

  - Can the element() function be combined with other values in the
content property? For example, content: "Hello" element(foo) "world"?

  - Prince does not support the dotted, solid and space keywords for
leader. Does treating solid as underscore really produce good results?

  - The section on the footnote area refers to the "default style
sheet", however this sounds meaningless, as CSS has no such thing, only
document languages can have default style sheets. You could just say
that float defaults to "bottom page" for @footnote, just like text-align
has different default values for @top-left and @top-right.

  - @footnote { float: bottom left column } looks quite scary to
implement, even though it does make sense for authors. We'll see.

  - In 6.3 border-length, it refers to the name as border-width.	

  - 6.6 counting footnotes refers to putting counter-increment inside a
@footnote rule. It's not clear whether this is a @page { @footnote {}}
rule or a different one at the top level. Also, Prince increments the
footnote counter for footnotes automatically.

  - The second example in 6.6 refers to reset-counter instead of

  - "If there is a footnote call on a page, the footnote area may not be
empty, unless its ‘max-height’ is too small." I think that it is easy to
break this rule, eg. by making a very very tall line of text that has a
footnote call on it and takes up the whole page, leaving no space for
the footnote at the bottom. We ran into this when we added footnotes to
Prince, and we just move the footnote to the next page in this case.

  - "Should there be a mechanism to create new areas like
footnote/sidenote, or are two "magic" area enough?" One could imagine
adding one extra keyword: @area footnote { ... }; however, it can be
tricky to balance genericity with support for all the footnote details.

  - On that note, there does seem to be heaps of overlap between
footnotes, running elements, target-move() and named flows.

  - For the hyphens property, the manual keyword manages to carefully
avoid mentioning the soft hyphen character at all. Is this intentional?

  - There needs to be a mention of how @counter-style rules interact
with @import rules.

  - The symbol() value is sometimes called symbols(); which is correct?
Prince supports symbols() and repeat().

  - 13 Page floats: s/lease/least/.

  - Regarding unless-room, presumably it means the element must fit in
its entirety on the current page, eg. not be split?

  - bookmark-label should take any value that content can take.

  - Do continuation markers need to apply to column breaks as well?

  - "To avoid these limitations, the beginning of a change mark is
associated with one document and the end of a change mark is associated
with another document." s/document/element/?

  - The default style sheet at the end should really be split: the h1,
h2 rules are HTML/XHTML specific, while the other rules give special
default values for properties in certain pseudo-elements.



Print XML with Prince!
Received on Monday, 7 May 2007 11:47:53 UTC

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