This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8862 - 0 as a value for number-rows-spanned, or all?
Summary: 0 as a value for number-rows-spanned, or all?
Status: NEW
Alias: None
Product: XSLFO
Classification: Unclassified
Component: XSL-FO (show other bugs)
Version: 2.0 Working Draft
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Liam R E Quin
QA Contact: Mailing list for comments on XSL (XSl-FO)
Depends on:
Reported: 2010-02-01 23:02 UTC by Liam R E Quin
Modified: 2010-04-22 10:56 UTC (History)
3 users (show)

See Also:


Description Liam R E Quin 2010-02-01 23:02:30 UTC
For spanning all rows in a table, should we
(1) use "0" as number of columns spanned, as does HTML
(2) allow "all" as a much clearer value, or
(3) both?
Comment 1 Klaas Bals 2010-02-17 07:04:14 UTC
I think it is appropriate to allow both. "0" for compatibility reasons and "all" for consistency reasons.
Comment 2 Edward Jiang 2010-03-31 18:23:46 UTC
This is a hard call.

I would recommend to support "0" only, although I agree that "all" is more intuitive, but it introduces datatype inconsistency. Therefore, it would potentially force some implementations to rewrite their current logic when they parse the value of ""number-rows-spanned" and "number-columns-spanned".

E.g., an old Java implementation naively uses Integer.parseInt() to convert the string to an integer, and ignore any value that's littler than 1. "0" would still work, but "all" will cause this java statement to throw a NumberFormatException, and it may not catch the exception yet in its implementation.

Comment 3 Tony Graham 2010-04-22 10:56:08 UTC
IMO, adding 'all' is not too much of a stretch for a XSL FO implementation.

Looking at the table at, there are existing properties with values that are either a numeric value or a keyword, e.g., 'border-*-precedence'. 'font-size-adjelt', 'hyphenation-ladder-count', and 'z-index'.