- From: Zhang, Zhiqiang <zhiqiang.zhang@intel.com>
- Date: Thu, 13 Nov 2014 08:20:49 +0000
- To: Arthur Barstow <art.barstow@gmail.com>, "Zhao, Tina" <tina.zhao@intel.com>, Simon Pieters <simonp@opera.com>, Odin H?rthe Omdal <odinho@opera.com>
- CC: public-webapps <public-webapps@w3.org>
Hi Art,
Sorry for missing this mail thus so late response.
> From: Arthur Barstow [mailto:art.barstow@gmail.com]
> Sent: Tuesday, October 28, 2014 23:26
> Would you please take a close look at following TIMEOUT failures:
>
> 1. eventsource/dedicated-worker/eventsource-constructor-non-same-
> origin.htm
Per the talk at [2], this test and 3rd one listed below failed the CORS check for fetchFail("https://example.not/test")
We may need to re-evaluate the tests, however, because the latest editor draft [3] has removed this statement in the CR [4]:
[[
This constructor must be visible when the script's global object is either a Window object or an object implementing the WorkerUtils interface.
]]
Thoughts, Simon & Odin?
> 2. eventsource/format-field-retry-bogus.htm
Latest Firefox Nightly gets PASS by manually running this test; so can revise the test result.
The failure may be caused by short timeout setting for automatically running the test. Will provide a fix after the test runner comes up to use [5].
> 3. eventsource/shared-worker/eventsource-constructor-non-same-
> origin.htm
>
> Perhaps these TIMEOUTs are caused by some factor other than an
> implementation bug (f.ex. the test case has a bug, the timeouts are
> caused by some "environmental" factor).
>
> -Thanks, Art
>
> [1] <http://w3c.github.io/test-results/eventsource/less-than-2.html>
[2] http://lists.w3.org/Archives/Public/public-webapps-testsuite/2013Aug/0017.html
[3] http://dev.w3.org/html5/eventsource/
[4] http://www.w3.org/TR/2012/CR-eventsource-20121211/#dom-eventsource
[5] https://github.com/w3c/web-platform-tests/issues/1372
Received on Thursday, 13 November 2014 08:21:36 UTC