Let's start with agenda item #3 Spring Cleaning

Since this has alot of discussion...

I agree that with jgraham's last comment about the whole point is to not have tests running on w3.org for security reasons.

<jgraham> I think Aryeh's request is reasonable

<jgraham> To run hgweb on w3c-test.org

<jgraham> I guess we need to ask plh/systeam

I am open to this as well...

Yes it shoud be a system/w3c team ask to get this in place

So that one can just expect /resources/ to work

Then everyone can really use this as the way to include testharness.js,etc...

Though this doesn't seem to block fixing tests in the HTML test suite

Let me take a quick peek at webapps and see what we have...

Since I was under the impression that Aryeh's issue was limited to his editing and dom4 work

<jgraham> Yes, I'm not sure exactly what his usecase is but he seems to particularly want to link to specific revisions of the editing testsuite

OK taking a peek at tests that have been submitted in webapps, I only see one for shadowdom that has an odd path to testharness.js

Some websocket tests do point to w3c-test.org, but they don't have the same constraint as the editing/selection tests that Aryeh has mentioned.

So it seems fine to update the tests in webapps and html to use /resources/

Do you agree james?

<jgraham> Yes

<jgraham> Are you also going to fix the relative order of testharness and testharnessreport.js?

I should be able to do that as well...

It should be easy though if I hit an issue I'll just update the path

sound good?

<jgraham> Yup

Agenda Item #2 New Test Submissions

http://dvcs.w3.org/hg/html/shortlog shows one new test for an Opera 'feature' by Ms2Ger

http://dvcs.w3.org/hg/html/rev/1c74dd6990e9

http://www.w3c-test.org/html/tests/submission/Ms2ger/the-elements-of-html/scripting/the-script-element/script-onload-string.html

James do you understand his comment about a Opera 'feature'?

<jgraham> Yup

<jgraham> It is a test that Opera fails because we implement some behavior that isn't in the spec

<jgraham> I will check and see if we have a bug on fixing it

<gsnedders> (Isn't that theoretically a permissable extension, therefore?)

<jgraham> No

<jgraham> The HTML spec doesn't work like the ES spec

<jgraham> It could be a permissable extension if we wrote a spec for it and got people to agree to implement that spec rather than HTML5

<jgraham> (on this point)

<jgraham> But we're not going to :)

Next Agenda Item: Bugs on Approved Tests

tinyurl -> http://tinyurl.com/6mvghxx

We have no new bugs

Shall we adjourn or does anyone have any other items they would like to discuss?

<jgraham> I don't have anything in particular I don't think

Ok let's adjourn

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: krisk
Inferring Scribes: krisk

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: gsnedders jgraham
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Agenda: http://lists.w3.org/Archives/Public/public-html-testsuite/2012May/0008.html

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 08 May 2012
Guessing minutes URL: http://www.w3.org/2012/05/08-htmlt-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report