RE: Google Audio/Video Tests (fixes and getting them approved)

The goal of these tests is to test the HTML5 audio/video features and not to test the optional/under discussion/proposed  addEventListner changes.

Being consistent with previous discussions in the group, I have updated the tests to include this parameter so that a 1/3rd of the tests don't fail on user agents that expect 3 parameters.
Note that is the same reason that we don't use onerror in our harness.


-----Original Message-----
From: James Graham [] 
Sent: Friday, March 04, 2011 1:49 AM
To: Anne van Kesteren
Cc:; Kris Krueger
Subject: Re: Google Audio/Video Tests (fixes and getting them approved)

On 03/04/2011 10:30 AM, Anne van Kesteren wrote:
> On Thu, 03 Mar 2011 18:05:56 +0100, Kris Krueger <>
> wrote:
>> As discussed in the recent conf calls we have consensus to update all
>> of the video test submissions so that they include a third parameter
>> for addEventListner.
>> I updated one test as an example -

>> If you have any feedback on the google a/v tests please send them to
>> the list.
>> We are going to move to have them all approved (minus feedback) on
>> March 22nd.
> Both DOM Level 3 Events and DOM Core make that parameter optional so I
> think the tests are correct. Of course in contemporary browsers they
> might run better with that parameter not omitted, but I am not sure that
> should be a criteria.

I think unnecessarily breaking things that aren't explicitly being 
tested is bad. In this case there is a clear workaround, so the tests 
should be fixed.

Received on Tuesday, 22 March 2011 05:56:15 UTC