W3C home > Mailing lists > Public > xsl-editors@w3.org > July to September 2006

Re: keep-*="always" seems to be ambiguous

From: Giannetti, Fabio <fabio.giannetti@hp.com>
Date: Wed, 12 Jul 2006 16:16:57 +0100
Message-ID: <DE62D3D0BDEF184FBB5089C7D387C374C13133@sdcexc04.emea.cpqcorp.net>
To: <dev@jeremias-maerki.ch>, <xsl-editors@w3.org>

Jeremias,
  both the behaviours are valid and compliant with the specs.

"1. keep conditions with a strength of "always" may never be relaxed
simply based on the value's name: "always". Only numeric keep strengths
may be relaxed."

This behaviour is supported by:

4.8 Keeps and Breaks

Keep conditions are imposed by the "within-page", "within-column", and
"within-line" components of the "keep-with-previous", "keep-with-next",
and "keep-together" properties. The refined value of each component
specifies the strength of the keep condition imposed, with higher
numbers being stronger than lower numbers and the value always being
stronger than all numeric values."

Stating that "always" has to be considered the highest priority.
On the other hand in:

3 Introduction to Formatting

Formatting is the process  ....
Constraints might conflict to the point where it is impossible to
satisfy them all. In that case, it is implementation-defined which
constraints should be relaxed and in what order to satisfy the others.

the case where the keep generates an overflow, put the rendering engine
in an over-constrained situation. This means that is up to the rendering
engine to decide which is the most appropriate action to execute, so
the:

"2. keep conditions with a strength of "always" may be relaxed if they
cannot be satisfied."
fall in this scenario.

Hope this helps,
Fabio Giannetti
Received on Wednesday, 12 July 2006 15:17:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:58 GMT