W3C home > Mailing lists > Public > public-css-testsuite@w3.org > April 2017

Re: nav-down-012 test issue

From: Dawid Błachut <d.blachut@adbglobal.com>
Date: Wed, 5 Apr 2017 12:47:22 +0200
To: Florian Rivoal <florian@rivoal.net>
CC: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <1261a9aa-0343-10c0-306e-97bf2bb06669@adbglobal.com>
Dear Florian,

thank you for your answer, I did not know about the github repository.

There is another issue in this test, inside 
css/css-ui-3/support/nav-up-012-frame.html. '<target-name>' 
<https://www.w3.org/TR/css-ui-3/#typedef-target-name> should be a 
<string> <https://www.w3.org/TR/css3-values/#string-value>, so it would 
need to be enveloped with double quotes or single quotes.

Unless the test checks how browser handle such situation, but it is not 
clear form the description that it should test that behavior 
('Assertion:' field).

I have another overall comment on the directional navigation tests. In 
my opinion it would be great to add some css rule that make the focused 
elements more visible (e.g. change the background), since this is not 
clear which one is currently focused while testing.

:focus {
     background-color: yellow;

If you want I can submit this as two separate issues in github.


On 05.04.2017 10:04, Florian Rivoal wrote:
> Dear Dawid,
> Thank you for reporting this mistake. I've made a correction, which 
> will be incorporated to the test suite once someone reviews it
> https://github.com/w3c/web-platform-tests/pull/5377
> Despite what you were led to believe by the shepherd test system at 
> http://test.csswg.org/shepherd/, this is no longer the place to submit 
> feedback about tests. The right way nowadays is to submit issues on 
> https://github.com/w3c/web-platform-tests (the css tests are in the 
> css/ subdirectory). You do not need any particular access rights to 
> report issues (or send change requests) there.
> Documentation for the w3c testing effort (including css) is at 
> http://web-platform-tests.org/
> Peter, could we update shepherd to somehow point people to the right 
> place?
> —Florian
>> On Apr 3, 2017, at 23:33, Dawid Błachut <d.blachut@adbglobal.com 
>> <mailto:d.blachut@adbglobal.com>> wrote:
>> Dear Sir / Madam,
>> I would like to report an issue with test: 
>> http://test.csswg.org/shepherd/testcase/nav-down-012/
>> #start element has nav-down CSS property set, but description says:
>> "Test passes if navigating *_up_* once moves the focus to the 
>> "FINISH" link."
>> I was not able to report issue using "Report Issue" button, as I have 
>> "Insufficient access privileges to add comments" after creating an 
>> account.
>> I would appreciate if you could provide me with rights to comment on 
>> test cases.
>> Thanking you in advance.
>> Yours faithfully,
>> Dawid Błachut
>> *
>> connecting lives*
>> connecting worlds
Received on Wednesday, 5 April 2017 10:49:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 April 2017 10:49:39 UTC