W3C home > Mailing lists > Public > public-css-testsuite@w3.org > September 2010

Re: Issue 144 resolved as undefined

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 01 Sep 2010 14:50:26 -0700
Message-ID: <4C7ECAA2.1090606@inkedblade.net>
To: Arron Eicholz <Arron.Eicholz@microsoft.com>
CC: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>, "James Hopkins (james@idreamincode.co.uk)" <james@idreamincode.co.uk>
On 08/27/2010 02:50 PM, Arron Eicholz wrote:
> With issue #144[1] being left undefined per the meeting notes[2] from
> the CSS F2F meeting in Oslo, it seems as if the
> text-decoration-visibility-### cases need updating. I figured I should
> notify you so you know the updates that need to be made in order for the
> cases to be valid again. It should be a simple change. I think in most
> cases you can just change “must” to “may” (don’t forget to add the “may”
> flag too).
>
> 1. http://wiki.csswg.org/spec/css2.1#issue-144
>
> 2. http://www.w3.org/2010/08/23-CSS-irc
>
> 07:45:39 <TabAtkins_> RESOLVED: Leave issue 144 officially undefined,
> add a note that it will be resolved in css3.

I think it would be better to drop these tests from the CSS2.1 build,
and revisit again for CSS3. A testcase with "may" is supposed to indicate
preferred behavior, and we don't yet know what the preferred behavior
will be.

~fantasai
Received on Wednesday, 1 September 2010 21:51:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 17:52:03 GMT