CSS Test: page-break-before explicit auto test


Melinda Grant, 2008/08/13 18:48

OK, it looks like the -a version leaves pba at its initial value, and this test sets it, to prove that the results are the same.

'auto' neither forces nor forbids a page break. You've covered the 'doesn't forbid' part, but I think we still need to prove it doesn't force a page break. If you separate the first two sentences of the description, putting them into two different divs, that will prove that the div doesn't force a page break.

Tom Clancy, 2008/08/29 11:12

I made that change, but at least in Prince it's not clear that it proves anything as Prince pushes the second div onto page 2 (I imagine due to the 'height: 100%' setting). Should I change the language/ modify the margins?

Melinda Grant, 2008/09/18 19:38

Change the style rules to: (a) set a class or an id for the first div rather than applying to all divs. Use a negative bottom margin of -4em rather than a negative top margin. (As it is, the content of the first div is pushed up off the top of the page. And, as you suggest, Prince is quite likely pushing the second 100%-high div to the next page.) (b) set a 7% page margin so that the text from the second div doesn't use up all available lines on 4x6in media. The second div proves that 'page-break-before' doesn't have an initial value of 'always'. The 'p' needs to split between pages to prove that it isn't 'avoid'. So lose the verbiage about it being ok if all lines are pushed to the next page. Orphans defaults to 2, so you must leave room for at least two 'dummy's plus however many lines of text will be needed for the description. -4em bottom margin with 7% page margin works at 4x6in and should be reasonable. (Works on Prince and HP, haven't tested others.)

Similar logic change needed for -a.

Tom Clancy, 2008/09/30 10:41

Made a bit of change in approach (based on the discussion here) for both this and http://wiki.csswg.org/test/css2.1/submit/9.

Melinda Grant, 2008/10/22 19:46

Lose the 'size'. (Sorry, I didn't mean in my comments above that you should make it a 4×6 text, just that we needed to ensure it worked across sizes.)

I don't think we need the font size. Am I missing something?

Going with the inherit-down-from-html approach again, lose the 'page-break-before: always' and change the 'page-break-before: auto' to 'page-break-before: inherit'.

Tom Clancy, 2008/10/27 10:50

I stripped the size and font-size, but left the explicit page break calls as this test pairs with http://wiki.csswg.org/test/css2.1/submit/9. 9 tests the inheritance, this explicitly forces 'auto'. Hoping that makes sense.

Melinda Grant, 2008/11/05 15:47

I'm not sure what the original design intent was with the two tests. I assumed it was: (1) show that not setting 'page-break-inside' results in behavior that neither forces nor forbids a page break. (2) show that setting 'page-break-inside: auto' results in the same behavior. (3) conclude that the initial value of 'page-break-inside' is 'auto'.

But the 'inherit from html' technique for proving initial value is clearly preferable, because there's no chance of user or UA stylesheets getting involved, and we can prove in one test what would otherwise require two.

I suggest we lose this test and rename the -a version to remove the -a.

You could leave a comment if you were logged in.
test/css2.1/submit/112.txt · Last modified: 2014/12/09 15:48 by
Recent changes RSS feed Valid XHTML 1.0 Valid CSS Driven by DokuWiki