W3C home > Mailing lists > Public > public-css-testsuite@w3.org > June 2015

Re: Scroll bar issue in long page of ref case

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Wed, 24 Jun 2015 12:12:21 -0400
To: "Xu, JianfengX" <jianfengx.xu@intel.com>
Cc: Public CSS Test suite mailing list <public-css-testsuite@w3.org>
Message-ID: <65a7d0caaa86fa3b8958d696afdbdef4@gtalbot.org>
Le 2015-06-24 05:16, Xu, JianfengX a écrit :
> Hi
>   When I use  automated ref test tool to run case
> @https:/github.com/w3c/csswg-test/blob/master/css-color-3/t424-hsl-values-b.xht<https://github.com/w3c/csswg-test/blob/master/css-color-3/t424-hsl-values-b.xht>
> and related ref case,





> I meet two issues.
> 1)      The page is too long to be displayed on the screen, so scroll
> bar show on the page.
>       On PC, the scroll bar always show.
> On android mobile, the scroll bar gradually disappear. But if you
> slide the page, the scroll bar show again.
>           When I use tool to get screenshot on android mobile,
> sometimes the screenshot has scroll bar, and sometimes not. This
> different lead to test fail.
> Due to browser which I use is based on webkit, I add a CSS style to
> the hide the scroll bar, then get pass result. The CSS style as below:
> ::-webkit-scrollbar {
>    width: 0px;
>    height: 0px;
> }

We do not recommend this.

The problem is the length of the test page. The problem is not the 
ability of an UA to generate a vertical scrollbar.

We also always want to avoid vendor-prefix in all tests... but that's 
another issue here.

> 2)      Because this page is too long and show scroll bar, which need
> user interaction to finish the testing. It is difficult to get
> screenshot which  cover the entire page.
> If a test needs user interaction, it cannot be automated by ref test.
> So, shall we rewrite (or split) the test/ref files?

Yes. Split the test and split the ref files.

When we use the Test harness, the iframe containing the test will use 
about 500px in height by the width of the window viewport. Anything 
taller than 500px will make the user using the Test harness scroll up 
and down... which is something we want to avoid.


Tests should be as short as possible. For reftests in particular 
scrollbars at 800×600px window size must be avoided unless scrolling 
behaviour is specifically being tested. For all tests extraneous 
elements on the page should be avoided so it is clear what is part of 
the test (for a typical testharness test, the only content on the page 
will be rendered by the harness itself).



<table border="border">

is not valid HTML5. Besides, it contradicts

line 6: table { border-spacing: 0; padding: 0; border: none; }

You can safely remove the 15 occurences of attribute specification 
border="border" in that test.

Test Format Guidelines

Test Style Guidelines

Test Templates

CSS Naming Guidelines

Test Review Checklist

CSS Metadata
Received on Wednesday, 24 June 2015 16:12:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:21 UTC