page-break-inside: avoid

[Thomas]

hi :-)

<http://www.haarbacher-trommel.de/aktuelles/jagd/jagerlobby-landratsamt-p
assau/>

why "page-break-inside: avoid" doesn't work ?

--
Téléassistance / Télémaintenance
http://www.portparallele.com/ThomasDECONTES/

[David E. Ross]

On 9/13/2009 3:55 AM, Thomas wrote:
> hi :-)
>
>
> <http://www.haarbacher-trommel.de/aktuelles/jagd/jagerlobby-landratsamt-p
> assau/>
>
> why "page-break-inside: avoid" doesn't work ?
>

This is bug # at <https://bugzilla.mozilla.org/show_bug.cgi?id=132035>,
which is now seven years old. This CSS2.1 capability is not getting
fixed because the drum beats louder for some CSS3 capabilities,
especially Web Fonts.

<rant>

I think this is a misallocation of resources since CSS2.1 is almost a
finished specification (missing a test suite) while Web Fonts (part of
the CSS3 Fonts Module) is nowhere near finished. Anyone who codes a
page-break style in a Web page according to the current specification
(candidate recommendation) is likely to find that, when that style is
supported by a browser, it will not change before the final release of
the specification (W3C Recommendation). Anyone who codes Web fonts in a
Web page according to the current specification (working draft), may
well find that the release of the W3C Recommendation (not even scheduled
yet) requires recoding the page. Similarly for browsers: Effort
towards complete implementation of CSS2.1 in a browser is not likely to
require changes when the CSS2.1 W3C Recommendation is released, but
efforts to implement Web fonts are likely to be ongoing for a series of
working draft specifications.

From the latest Cascading Style Sheets Level 2 Revision 1 (W3C Candidate
Recommendation 08 September 2009): "This is a W3C Candidate
Recommendation, which means the specification has been widely reviewed
and W3C recommends that it be implemented."

From the latest CSS Fonts Module specification (W3C Working Draft 18
June 2009):
"This is a draft document and may be updated, replaced or obsoleted by
other documents at any time. It is inappropriate to cite this document
as other than work in progress."

</rant>

--
David E. Ross
<http://www.rossde.com/>

Go to Mozdev at <http://www.mozdev.org/> for quick access to
extensions for Firefox, Thunderbird, SeaMonkey, and other
Mozilla-related applications. You can access Mozdev much
more quickly than you can Mozilla Add-Ons.

[David E. Ross]

Oops. I was so busy ranting that I left the bug number out of the first
line of my reply. It's #132035.