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

Re: Generated Content draft

From: Michael Day <mikeday@yeslogic.com>
Date: Wed, 4 Jun 2003 21:17:15 +1000 (EST)
To: Ian Hickson <ian@hixie.ch>
Cc: "www-style@w3.org" <www-style@w3.org>
Message-ID: <Pine.LNX.4.44.0306042109360.21245-100000@lorien.yeslogic.com>

> If the gencon draft is changed to use flow: and flow(), then documents
> written for Prince will render unexpectedly in compliant implementations,
> and vice versa.

Not if Prince is the first compliant implementation :)

> The result of IE4's premature implementation is that when the real spec
> came out, with its slightly different semantics, authors ended up writing
> documents that worked with IE4, and not with the spec.

Unlike IE, we have not yet reached 98% market dominance. Also unlike IE,
we actually keep an eye on the spec when we are developing.

> I presume the elements are also removed from the flow? i.e. elements are
> not duplicated?

Yes, they are removed from the flow.

> Do you support moving elements to other elements, or just to headers/
> footers? What happens to an element that isn't re-inserted?

No, just to headers and footers at present. Elements that are not
re-inserted vanish, I believe.

> top-far-left, top-left, top, top-right, top-far-right, left, (content),
> right, footnote, bottom-far-left, bottom-left, bottom, bottom-right,
> bottom-far-right, if I recall correctly. This is all subject to change, I
> do not know what the current state of the Paged Media module is.

Right. The working group activity is quite opaque to those who are not on
it, and our implementation activity may outpace the specification, at
least on the topic of paged media.

>    @counter sentence {
>      increment-at: final-position;
>    }

I have seen @counter rules referenced here and there, but never defined in
any specification ever (shrugs).

>    body::group(dt, dd) { display: block; border: solid; }
> ...but this runs into the "can't easily disable them" problem and is also
> quite hard to define usefully (what should the arguments be?).

Once CSS gets into serious document manipulation it becomes a lot harder
for the casual user to make sense of what is going on. Adding content to
the document with before/after/marker at least doesn't change what is
already there, but moving stuff around gets quite confusing.


YesLogic Prince prints XML!
Received on Wednesday, 4 June 2003 07:13:43 UTC

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