W3C home > Mailing lists > Public > public-css-testsuite@w3.org > October 2012

Re: Testing border-radius

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Sun, 21 Oct 2012 15:09:09 -0400
Message-ID: <20121021150909.10371upcycpxmbf9@ed-sh-cp3.entirelydigital.com>
To: "Kang-Hao (Kenny) Lu" <kanghaol@oupeng.com>
Cc: W3C CSS Test Suite mailing list <public-css-testsuite@w3.org>, TTWF - beijing <testwebforwardbeijing@googlegroups.com>, 小黄鱼 <liz@oupeng.com>
"Kang-Hao (Kenny) Lu" <kanghaol@oupeng.com> a écrit :

> In Test the Web Forward@Beijing, it was mentioned that the tests written
> should fail even when the browser doesn't support that feature *at all*.


As far as I am concerned and involved, such goal is a rule: you want  
only-CSS1-capable browsers and only-CSS2.1-capable browsers to fail  
such tests. Sometimes, such goal is not possible, achievable,  
therefore there are exceptions.

> I am wondering if this is necessary because it is not at all
> straightforward how you do this for 'border-radius'.
> The idea I just suggested to a participant is to add something like
>   <div id="dummy">
>     You would not see this if your browser supports 'border-radius'.
>   </div>
>   #dummy {
>     border-radius: 500em;
>     width: 10000em;
>     height: 10000em;
>     overflow: hidden; /* the text would be clipped */
>   }
> to the test and not to the reference, but as the name suggests, it's
> quite dummy.
> Given all browsers support 'border-radius' without prefix now, is
> something like the thingy above still necessary? And does anyone have a
> better idea?

If I understand your test - and I'm not sure that I do right now - ,  
this is an extreme and edge case.

Contributions to the CSS 2.1 test suite:

CSS 2.1 Test suite RC6, March 23rd 2011

CSS 2.1 test suite harness:
Received on Sunday, 21 October 2012 19:09:41 UTC

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