15:01:54 RRSAgent has joined #htmlt
15:01:54 logging to http://www.w3.org/2011/07/26-htmlt-irc
15:02:25 zakim, this is htmlt
15:02:25 krisk, I see HTML_WG(HTMLT)11:00AM in the schedule but not yet started. Perhaps you mean "this will be htmlt".
15:02:35 zakim, this will be htmlt
15:02:35 ok, krisk; I see HTML_WG(HTMLT)11:00AM scheduled to start 2 minutes ago
15:04:23 If plh atttends we can setup the conf call
15:04:46 I can dial in if someone wants to be on the conf call as well...
15:05:04 though I suspect this (like many other meetings) will be all on IRC
15:05:32 Agenda -> http://lists.w3.org/Archives/Public/public-html-testsuite/2011Jul/0009.html
15:06:06 Item #1 Check for any bugs on approved tests
15:07:13 Looking at Bugzilla I see no new bugs
15:07:15 http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=HTML+WG&component=testsuite&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=
15:08:42 Item #2 php submission for Async script ask
15:09:14 Has anyone submitted any php pages?
15:09:50 The w3c has this setup, I just have not had a need...
15:10:05 Though I do now for some async script tests
15:10:46 I just need to call sleep to help make the script downloads deterministic
15:11:18 What's the problem with it?
15:12:35 We submitted some PHP with the video preload stuff I think
15:12:59 I didn't do anything special. Was I supposed to ping plh or someone?
15:13:04 Did the php files just work?
15:13:10 I didn't check
15:13:21 In theory they should have to be reviewed
15:13:29 So hopefully not :)
15:13:33 I can just submit them and then ping plh
15:13:39 I think I once saw a note that an email was sent to reviewers when I pushed
15:14:02 Did yours just work?
15:14:34 Don't remember
15:16:18 I'll ping plh and send an email to the list
15:16:49 I noticed that the hg -> w3c-test stopped rsync'ing as well (was fixed)
15:17:15 Though jgraham noticed that scripts have the wrong content-type
15:17:37 For example http://w3c-test.org/html/tests/approved/common/media.js is being served as text/html
15:18:35 Which will also need to get fixed
15:18:46 Yes
15:21:11 Item #3 A few more test submissions have occured as well since we last met on July 12th (good)
15:21:45 Microsoft submitted 27 structured clone tests
15:21:49 See -> http://w3c-test.org/html/tests/submission/Microsoft/structuredclone/structuredclone_0.html
15:24:42 Jwatt are you just listening or do you plan on participating?
15:24:45 Ah, did you announce that on the list? Hopefully I will have a little time to review
15:25:03 I wonder if using ES5 features is really necessary
15:25:28 (to be clear I am not promising to review :)
15:26:09 And if setTimeout is necessary?
15:26:57 Thanks for looking at these tests...
15:27:15 though I think it's more intresting if the cloning is occuring as expected
15:27:34 E.g. should null be cloned?
15:27:42 Well yes, but I will need a proper amount of time to do that level of review :)
15:28:02 But hopefully I will have in the next days. We will see
15:28:29 any other agenda items? or shall we adjorn?
15:28:38 jwatt?
15:28:43 I'm almost ready converting my tests to testharness.js, btw
15:29:21 RRSAgent, make logs public
15:30:54 Meeting adjorned
15:30:56 rrsagent, generate minutes
15:30:56 I have made the request to generate http://www.w3.org/2011/07/26-htmlt-minutes.html krisk
15:32:55 Object.defineProperty(Custom.prototype, "b", { enumerable: true, value: 100 }); is the only unneeded use of the ES5 stuff as far as I can see.
15:33:09 Custom.prototype.b = 100; would be entirely equiv. to that
15:35:03 Seem reasonable to not use ES5 for these tests
15:35:34 BTW some of the review comments in the classList tests were fixed
15:35:40 The other ones using defineProperty are testing using non-standard attributes, which is interesting to test.
15:36:13 Same agreement that we have had in the past - e.g. don't use standards outside of HTML5 that don't work across the browsers
15:36:54 jgraham, going to look at those
15:37:47 krisk: The problem in this case is it is interesting, and likely by the time the testsuite is finished everyone will support ES5, so it's not an issue.
15:38:19 There are clearly ES5 things that should be tested for structured clone
15:38:44 It wasn't obvious to me those tests tested those things, but I didn't look too closely
15:40:35 jgraham: Only one of them didn't.
17:33:44 Zakim has left #htmlt