W3C home > Mailing lists > Public > public-webapps-testsuite@w3.org > January 2013

Re: RfR: Progress Events Test Cases; deadline January 28

From: Jungkee Song <jungkees@gmail.com>
Date: Sun, 20 Jan 2013 00:20:59 +0900
Message-ID: <CAGwV++dxkBBbFbgyp0R782DtLC2bqsnKBDfg9mDX5zoj0cbb3A@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: "public-webapps-testsuite@w3.org" <public-webapps-testsuite@w3.org>, public-webapps <public-webapps@w3.org>
On Sat, Jan 19, 2013 at 6:38 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
>
>> <http://w3c-test.org/webapps/ProgressEvents/tests/submissions/Samsung/>
>
> These are testing XMLHttpRequest. There are no normative criteria in
> the Progress Events specification that justify these tests.

I agree. It seems that .../submissions/Ms2ger test cases cover all the
normative criteria of Progress Events spec. Then, we can adjust the
scope of the RfR to Ms2ger's contribution. (I will fix the issue in
.../submissions/Samsung anyway.)

>  (This in
> part is why I merged Progress Events into XMLHttpRequest. On its own
> it's kinda useless.)

I believe Progress Events spec has a meaning as an event interface
definition itself as long as it would potentially support multiple use
cases (currently XHR and <img> element.)

> As for the tests, one is buggy because the PHP gives a 404.

I've pushed the php file in
<http://dvcs.w3.org/webapps/ProgressEvents/tests/submissions/Samsung/resources/>
but cannot find it at <w3-test.org> mirror. Can anyone help?

> Another
> one assumes the network is not slow by checking for ev.loaded != 0.

Fixed. https://dvcs.w3.org/hg/webapps/rev/52b745cebe4f

Thanks for comments.


Jungkee

>
>
> --
> http://annevankesteren.nl/
>



-- 
-----------------
Jungkee Song
Samsung Electronics
Received on Saturday, 19 January 2013 15:21:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 April 2014 14:15:59 UTC