RE: Some proposed tests

fantasai said: 

>  >     page-cb-000.xht
> 
> - Please remove all declarations in the @page rule (aside 
> from the "margin: 1in"
>    declaration. They will be added by the build scripts.

I thought we had said that the build scripts would not add header
content in the presence of an @page construct...?  Or were you thinking
that only applied to css3 paged media tests?  

We have talked about adding p or hn elements as the first and last
elements within the body, when margin box content is an explicit part of
the test design; but I wonder if it might not be better to let the
author decide where the test identifying information goes.

I guess we'd better decide on how we're going to do this before I
resubmit these...

Options would seem to be:

1. If there's no "@page", the build scripts add margin-box test
identification; else the author adds manually.
2. If there's no "@page", the build scripts add margin-box test id; else
the build scripts add leading and trailing <p>'s (or whatever) inside
the body.
3. If there's no "@margin-box" (where margin-box is replaced by one of
the 16 margin-box idents), the build scripts add margin-box test id;
else the author adds manually.
4. s/a 3, but scripts add leading and trailing p's, rather than the
author adding manually.
5. ???

I prefer #3, because it provides the best identification info with the
least author effort.  Having the test identification info is important
for pages other than the first and the last, but it's not available with
#2 or #4.  And keeping the test look-and-feel as consistent as possible
will help testers as well. The 'size' tests, for example, could benefit
from headers but won't have them if we go for #2 or #4.

But assuming it's too tedious to search for each of the 16 names of
margin-boxes, #1 would be my second choice.

We could choose different answers for CSS 2.1 and CSS 3, based on the
simplifying fact that margin boxes aren't available in 2.1, so we know
they won't be used as part of test design.  But I think it would be
preferable from a test authoring perspective to use the same approach
for both 2.1 and 3.

Best wishes,

Melinda

> -----Original Message-----
> From: fantasai [mailto:fantasai.lists@inkedblade.net] 
> Sent: Monday, August 20, 2007 12:54 PM
> To: Grant, Melinda
> Cc: public-css-testsuite@w3.org
> Subject: Re: Some proposed tests
> 
> Grant, Melinda wrote:
> > Attached are some proposed tests ready for review.
> >  
> > For CSS 2.1:
> >     page-left-right-000.xht
> 
> - The CSS indentation on this page is weird. Maybe use spaces 
> instead of tabs?
>    It doesn't line up very well with e.g. 8 spaces per tab.
> - I'd add
>      div {
>         color: blue;
>         text-align: center;
>      }
>    and use 60% instead of 50% in the margins to make the 
> alignment clearer
>    to the tester.
> 
>  >     page-cb-000.xht
> 
> - Please remove all declarations in the @page rule (aside 
> from the "margin: 1in"
>    declaration. They will be added by the build scripts.
> - The blue border will not show up at the bottom because 
> 'height: 100%' is
>    exclusive of borders. You could assign the borders to the 
> left and right
>    sides only and require that they extend the full height of 
> the aqua box.
>    Use a much thicker border, though.
> - The title should mention @page margins, as we probably want 
> to add a similar
>    test that doesn't depend on @page margins.
> 
> 
>  >     page-breaki-000.xht
> 
> - The title should be more specific, e.g. "page-break-inside: 
> avoid on lists"
> - The assertion should be more assertive:
>      "page-break-inside: avoid prevents breaking inside a list"
> - Don't use green for the box, green is used to indicate a 
> pass condition.
>    In this case you want to use gray, for descriptive lines.
> - The test works on a somewhat limited range of page sizes. One way to
>    increase the range of page sizes would be to use two boxes 
> that add up
>    to 100% height plus some negative margins, like this:
> 
>    body {
>       font-size: 10pt;
>       line-height: 1;
>    }
> 
>    .filler {
>       height: 50%;
>       border: 2pt medium gray;
>    }
>    .no2 {
>       margin-top: -38pt;
>    }
> 
>    <div class="filler">...</div>
>    <div class="filler no2"></div>
>    <ol> ... </ol>
> 
>    This ensures that there is exactly 30pt of space at the 
> bottom of the page,
>    no more, no less, no matter what size page we have (as 
> long as it's bigger
>    than 38pt), and the list will therefore always fall on the 
> page break.
>    You can then shorten the list to the first eight items so 
> that it will fit
>    entirely on smaller sheets as well.
> 
> >     page-first-000.xht
> 
> - Please remove all declarations in the @page rule (aside 
> from the "margin: 1in"
>    declaration. They will be added by the build scripts.
> - This is not a valid CSS2.1 test because the two pages have 
> different page area
>    widths, and support for that is not required. Having 
> uneven margins and swapping
>    which side is wider would be a valid test.
> - Specify the yellow color on html, not on body.
> - "This text must have a one inch margin" is not clear. Maybe 
> "the yellow box on
>     this page must have a one inch margin around it"?
> 
> > For CSS3 Paged Media:
> >     page-pseudo-000.xht
> 
> - Please remove all declarations in the @page rule (aside 
> from the "margin: 1in"
>    declaration. They will be added by the build scripts.
> - Use at least 50% for the margins, preferably 60%.
> - Use pts instead of px.
> - I suggest clarifying the descriptions as
>      "This text must be on the right side of the page, which 
> must have an orange
>       border entirely on the right half of the page."
>     and
>      "This text must be on the left side of a new (second) 
> page, which must have
>       a blue border entirely on the left half of the page."
> - Alternatively you could change this test to rely only on 
> border color + style,
>    since the CSS2.1 version above will be imported into this 
> test suite as well.
> 
> >     page-named-000.xht
> 
> - Please remove the first @page rule.
> - In the description, mention the exact text of the header so 
> it can be picked
>    out from the generated test headers. Also, remove the last 
> sentence and append
>    ", in a text size larger than this text" to the first sentence.
> - Don't use red for the header. Red is only used to indicate 
> failures. Use 'blue'.
> 
> ~fantasai
>

Received on Tuesday, 21 August 2007 23:41:53 UTC