14:58:35 <RRSAgent> RRSAgent has joined #htmlt
14:58:35 <RRSAgent> logging to http://www.w3.org/2012/09/25-htmlt-irc
15:01:01 <krisk> Like the many of the past meetings we'll do this on IRC
15:01:09 <krisk> unless someone objects
15:02:31 <krisk> Agenda -> http://lists.w3.org/Archives/Public/public-html-testsuite/2012Sep/0014.html
15:02:52 <krisk> First Agenda Item 'bugs on approved' tests
15:03:19 <krisk> We have a few more 'dom viewer' bugs have been opened
15:04:10 <krisk> Some of them look like possible interop bugs, though they are CSS tests and not HTML tests
15:04:20 <krisk> Though one is intresting https://www.w3.org/Bugs/Public/show_bug.cgi?id=18807
15:05:26 <krisk> maybe tests are being written on another planet?
15:06:34 <krisk> jgraham do you want to discuss bug 15041/15042?
15:06:59 <krisk> Looks like you re-opened bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=15042
15:07:23 <plh> plh has joined #htmlt
15:07:54 <krisk> good morning plh
15:08:13 <plh> good morning
15:08:18 <krisk> If you want to catch up we were just starting to look at new bugs
15:08:24 <plh> thank you
15:08:53 <krisk> A number of 'dom viewer' bugs were auto-opened
15:09:22 <krisk> Some are not tests rather just a joke or someone testing how dom view works?
15:09:30 <krisk> e.g. https://www.w3.org/Bugs/Public/show_bug.cgi?id=18807
15:09:49 <krisk> The others are really css bugs/tests and not html tests
15:10:06 <krisk> e.g. https://www.w3.org/Bugs/Public/show_bug.cgi?id=18944
15:10:52 <krisk> Though jgraham did re-open bug #15042  https://www.w3.org/Bugs/Public/show_bug.cgi?id=15042
15:11:35 <krisk> The bugs brings up a question about the html.next process
15:11:57 <krisk> The spec bug was resolved and the canvas update will occur in html.next
15:12:19 <krisk> Though right now we don't have a location to place html.next tests
15:12:35 <krisk> For example encrypted media, canvas 2.0, etc...
15:13:13 <krisk> I think we woud want a seperate location given the focus on completing html5 in 2014
15:13:33 <krisk> thoughts?
15:14:46 <krisk> Note the spec bug# is https://www.w3.org/Bugs/Public/show_bug.cgi?id=15041
15:21:50 <krisk> plh/jgraham do you want to discuss or shall we move on with the agenda?
15:23:25 <krisk> Ok then let's move on to the next agenda item
15:23:53 <krisk> Next Agenda Item New Test Submissions
15:24:26 <krisk> The only new updates/changes have been the audio and video tests from Intel
15:24:49 <krisk> Thiago Marcos P. Santos updated the tests per feedback from the group
15:25:22 <krisk> I looked at the tests did others look at these tests that Intel submitted?
15:26:59 <krisk> plh are you still online?
15:27:45 <plh> hi Kris. sorry, got distracted here
15:27:50 <krisk> NP
15:28:28 <plh> did you run the Intel tests?
15:28:43 <krisk> Yes on a few browsers
15:29:06 <krisk> webkit pass them all (not a surprise since Intel submitted the tests)
15:29:30 <krisk> Other browsers have common interop issues - defaultMuted
15:29:38 <krisk> http://www.w3c-test.org/html/tests/submission/Intel/video/video_defaultMuted_reflect.html
15:30:11 <plh> this one is ok on gecko and webkit at least
15:30:16 <krisk> and then the other issue is the mediaGroup attribute
15:30:31 <plh> as well as opera
15:30:33 <krisk> Though they are valid tests so I think we should approve
15:30:38 <plh> +1
15:30:46 <krisk> See http://www.w3c-test.org/html/tests/submission/Intel/video/video_attributes.html
15:30:57 <plh> some of the tests are human tests
15:31:13 <plh> at some point we should separate the tests into different categories
15:31:22 <krisk> yes
15:31:52 <krisk> Some test unfortunatly will be 'human' tests - for example application cache
15:32:23 <plh> yes
15:32:24 <krisk> For context we are looking at 'both' the audio and video test from intel
15:32:38 <krisk> http://www.w3c-test.org/html/tests/submission/Intel/video/
15:32:53 <krisk> http://www.w3c-test.org/html/tests/submission/Intel/audio/
15:32:58 <plh> yep, saw that
15:33:19 <krisk> Did you see the other comment above about html5 vs html.next tests?
15:33:40 <plh> ah, I saw the thread on the list
15:33:46 <plh> and was thinking about that indeed
15:34:03 <plh> yes, we need two buckets now
15:34:34 <plh> honestly, it might be good to adopt the approach of the html editors
15:34:44 <plh> and possibly switch to github
15:34:59 <krisk> I'm sure this will be a discussed at TPAC
15:35:24 <plh> I'm hoping that Robin will have some time in October to propose a new approach
15:35:50 <plh> and figure out how to set things up
15:37:23 <krisk> OK
15:37:46 <krisk> Do we want to discuss other items or shall we adjorn?
15:38:02 <krisk> Note that TPAC registration is open
15:38:47 <krisk> http://www.w3.org/2012/10/TPAC/
15:38:55 <krisk> and closes on oct 16th
15:39:26 <krisk> Also a 'test the web forward' event will occur right before TPAC in Paris
15:39:34 <krisk> http://testthewebforward.org/
15:39:39 <krisk> OK
15:40:26 <krisk> This will be a good time to have people learn and write tests for the HTML WG and WebApps WG
15:40:43 <plh> yes. I won't be in Paris but Robin will be there
15:41:13 <krisk> nice
15:41:22 <plh> feel free to use any of the slides at http://w3c.github.com/testing-how-to/#
15:41:28 <krisk> thx
15:41:52 <krisk> any other items people would like to discuss?
15:42:07 <plh> not on my side
15:42:57 <krisk> PLH note that I have been updating the wiki everytime we approve tests
15:42:58 <krisk> http://www.w3.org/html/wg/wiki/Testing
15:43:20 <plh> ah thx
15:43:26 <krisk> Which has the total approved tests (11,642) and features that are tested in the test suite
15:43:34 <plh> I need to update w3c-test.org I think
15:43:54 <plh> I don't believe that the approved tests known by the framework are up-to-date
15:44:01 <krisk> That is correct
15:44:28 <krisk> Though I don't believe we have consensus to have people submit results 
15:44:49 <krisk> e.g. Apple would not approve that someone submitted test results for Safari
15:45:25 <plh> something to talk about at TPAC I guess
15:46:07 <plh> with HTML5 wanting to move to CR by the end of the year, we'll need to figure which feature needs to be on the at risk list
15:46:15 <plh> and having test results will help with that
15:46:40 <krisk> Correct it's part of the HTML5 2014 plan - it's really what the report looks like?
15:47:39 <plh> not sure I understand your question
15:47:54 <krisk> It could be done w/o actuall browser names, since all the WG should care about is knowing that at least two browsers pass a test
15:48:22 <plh> correct
15:48:28 <krisk> At least to enter CR
15:49:40 <krisk> I also recall some specifics that the browser can't be a nightly?
15:49:59 <plh> to exit CR, yes
15:50:05 <plh> but that's not a problem for now
15:50:18 <krisk> Agree
15:50:25 <plh> if it's a nighly today, there is a good change it will be in a stable version later
15:50:56 <plh> s/change/chance/
15:52:06 <krisk> any other business to discuss or shall we adjourn?
15:52:17 <plh> let's adjourn
15:52:38 <krisk> RRSAgent, make logs public
15:52:45 <krisk> rrsagent, generate minutes
15:52:45 <RRSAgent> I have made the request to generate http://www.w3.org/2012/09/25-htmlt-minutes.html krisk
15:52:58 <krisk> meeting adjourned
15:55:06 <Ms2ger> Ms2ger has joined #HTMLT
16:05:17 <krisk> Take a peek at the comments about bug 15042 that you re-opened
17:20:31 <Ms2ger> Ms2ger has joined #HTMLT