W3C home > Mailing lists > Public > www-style@w3.org > November 2004

Re: [CSS21] possible spec error re page-break properties

From: Syntactic: Jim Wilkinson <syntactic@btinternet.com>
Date: Tue, 02 Nov 2004 12:21:41 -0000
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <opsgt7afvybrj5zx@host213-122-57-25.in-addr.btopenworld.com>

I'm tying off this thread for the benefit of anyone reading the archive. I  
didn't receive a response from the WG on-list so I mailed Bert Bos  
directly. Briefly, it concerns the apparent inapplicability of the  
page-break properties to <tr> elements.

> What I'm looking for is acceptance (or rejection) by W3C that there
> is an error/omission/unclarity in the specs. I haven't commented
> whether the errors should be fixed (e.g. in CSS21) ...The fix would be  
> unambiguously to allow
> or to disallow page-break properties to apply to <tr> (and to other
> table-type elements). That decision is W3C's prerogative (but taking
> all views into account of course). My personal view is that it
> probably should be fixed in CSS21 (since content authors and browser
> manufacturers will have to work to that spec for several years to
> come) and that the fix should be to disallow (since that will render
> only Opera noncompliant - ironically).

Bert kindly responded:-

"It seems reasonable to allow 'page-break-inside' to apply to table rows.  
I'll add it to the issues list."

I should explain that my limited testing shows that only Opera implements  
the obviously desired behaviour of honouring page-break-inside on <tr>.  
The difficulty is that changing CSS21 to require it would render all(?)  
UAs except Opera non-compliant; CSS21 is intended to reflect current UA  
practice.

--
Jim Wilkinson

Cardiff, Wales UK

Opera e-mail client: http://www.opera.com/m2/
Received on Tuesday, 2 November 2004 12:21:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:34 GMT