Looks like this will be all on IRC

Normal given the past meetings...

Agenda http://lists.w3.org/Archives/Public/public-html-testsuite/2011Sep/0001.html

Looks like a light meeting agenda...

Item #1 Check for and bugs on approved tests

Bug #12896 (old)

I recall that we were going to have plh come back to confirm that this is true

I'll send this out in the meeting notes since it's been a little while

I presume that Ms2ger believes that this is a valid bug since he opened the bug

If anyone else has feedback please respond either to the IRC, Meeting notes or in the bug itself

I'll add this to the next meeting to help drive this bug to closure

<Ms2ger> Actually

<Ms2ger> getElementsByClassName is now defined in DOM Core instead of HTML

<Ms2ger> So I'll move these tests to the WebApps repo

You should ping the Opera folks since the wrote most of the tests

<Ms2ger> jgraham, ^

IMHO standard practice is to remove tests if they are no longer normative

Bug #13875

Ms2ger could you send something to the list or add to the bug maybe a use case using httpd.js vs php?

<Ms2ger> Haven't had time to spend on that yet

Ok

Looks like you fixed/updated some canvas tests

(you meaning ms2ger)

<Ms2ger> I did

The TYPE_MISMATCH_ERR should be noted

Do you want to add more to the IRC on these changes?

<Ms2ger> No

Any reason?

The reason I ask is that this error case had really good browser interop (chrome, IE, Firefox, Opera)

<Ms2ger> Oh

No this is not the case...the IDL spec is leading - which seems odd

It would be alot easier to have the IDL spec just match all the browsers and canvas content on the web

<Ms2ger> It doesn't really matter which exception is thrown, IMO

<Ms2ger> Might as well pick a logical one

e.code == 17 (TYPE_MISMATCH_ERR) seems just fine

<Ms2ger> Anyway, if you think it's an issue, it's a spec issue

If we just care that an assert is thrown then the HTML test should be updated as such

Seems like it would be more valid to have some IDL cases in webapps rather then trying to test the web IDL spec via HTML tests

<Ms2ger> WebIDL is a normative dependency for HTML, so we should test the implications of that

That is fine just ned to call this out - better to be clear that this is a web IDL test case and not a HTML test case

<Ms2ger> It is an HTML test case

<Ms2ger> It is testing an interface defined in HTML

Still seems like a spec bug in IDL

<Ms2ger> I think TypeError makes more sense when you pass a value that doesn't match the type of the parameter, but please file a bug on WebIDL

Moving on Agenda Item #2 new test submissions

Any comments on test submission that people may want to be informed of?

<Ms2ger> Nothing in particular

OK - people can always look at the 'shortlog' http://dvcs.w3.org/hg/html/shortlog

Thats the end of the agenda

shall we adjourn?

<Ms2ger> OK

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: Ms2ger
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


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

Got date from IRC log name: 06 Sep 2011
Guessing minutes URL: http://www.w3.org/2011/09/06-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