- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Thu, 21 Feb 2013 06:59:14 -0500
- To: ext Jungkee Song <jungkee.song@samsung.com>
- CC: "'Ms2ger @ Mozilla'" <ms2ger@gmail.com>, public-webapps-testsuite@w3.org, cpgs@samsung.com
On 2/21/13 1:13 AM, ext Jungkee Song wrote: >> -----Original Message----- >> From: Arthur Barstow [mailto:art.barstow@nokia.com] >> Sent: Thursday, February 21, 2013 3:40 AM >> >> Jungkee - it appears there is quite a bit of implementation work needed >> before this spec can exit CR. Do you have any data regarding a timeline >> for when the implementations will be updated to conform to the CR? >> > I think the timeline would be depending on the browser vendors and WebKit > community. Anyway, I'll filing the bugs soon and share the status keeping my > eyes on the feedbacks. Sounds good; thanks. >> FYI, I created the document >> <http://www.w3.org/wiki/Webapps/Interop/ProgressEvents> to summarize the >> status of the tests based on this thread. (A few followups below.) >> > Thank you so much. I think test case #1 and #6 in constructor.html should be > moved to DOM spec test. It is resorting to the implementation of Event > interface. E.g., WebKit Event implementation does not even have isTrusted > attribute at the moment. Please copy interface.html to the approved directory <http://w3c-test.org/webapps/ProgressEvents/tests/approved/>. If no one objects to removing #1 and #6 from constructor.html before Feb 24 then please put a version of that file in the approved and only include the other tests. After the approved file are in place, one then needs to update <http://w3c-test.org/webapps/ProgressEvents/tests/Status.html> and <http://www.w3.org/wiki/Webapps/Interop/ProgressEvents>. -Thanks, Art
Received on Thursday, 21 February 2013 11:59:51 UTC