wann wird CSS 2.0 standard sein?

[MudGuard]

Hi,

es geht zum beispiel speziell um page-break-befor:avoid & page-break-after:avoid

oder könnter es eventuell daran liegen, dass ich diese angaben in einem <tr>-tag gemacht habe?

Bingo.

'page-break-before'
    Value:   auto | always | avoid | left | right | inherit
    Initial:   auto
    Applies to:   block-level elements
    Inherited:   no
    Percentages:   N/A
    Media:   visual, paged

'page-break-after'
    Value:   auto | always | avoid | left | right | inherit
    Initial:   auto
    Applies to:   block-level elements
    Inherited:   no
    Percentages:   N/A
    Media:   visual, paged

'page-break-inside'
    Value:   avoid | auto | inherit
    Initial:   auto
    Applies to:   block-level elements
    Inherited:   yes
    Percentages:   N/A
    Media:   visual, paged

Alle page-break - Properties sind also nur für block-level-Elements erlaubt. (siehe http://www.w3.org/TR/REC-CSS2/page.html#propdef-page-break-after)

Block-level elements are those elements of the source document that are formatted visually as blocks (e.g., paragraphs). Several values of the 'display' property make an element block-level: 'block', 'list-item', 'compact' and 'run-in' (part of the time; see compact and run-in boxes), and 'table'.

Also sind nur die Elemente block-level, die bei display einen der Werte block, list-item, compact, run-in oder table haben (siehe http://www.w3.org/TR/REC-CSS2/visuren.html#block-level)

tr dürfte aber display:table-row; haben...

Damit darf page-break-after/page-break-before/page-break-inside gar nicht auf tr angewendet werden.

cu,
Andreas