W3C home > Mailing lists > Public > public-html-testsuite@w3.org > September 2010

RE: HTML Testing Task Force Conf Call Agenda 9/21/2010 (Notes)

From: Kris Krueger <krisk@microsoft.com>
Date: Thu, 30 Sep 2010 00:36:40 +0000
To: Kris Krueger <krisk@microsoft.com>, "'public-html-testsuite@w3.org'" <public-html-testsuite@w3.org>, "Philip Taylor <pjt47@cam.ac.uk> (pjt47@cam.ac.uk)" <pjt47@cam.ac.uk>
Message-ID: <FA9085650D2F8B4A9D501ED9D9706E9A14B1986F@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Notes 

* Agreed that http://test.w3.org/html/tests/submission/Microsoft/video/video_008.htm is now correct
* Ask Simon Pieter to look at the update to http://test.w3.org/html/tests/submission/Microsoft/video/video_006.htm
* Philip's Canvas tests (Next 25 Tests)
	#1 http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/toDataURL.jpeg.quality.basic.html
	Need to have Philip update the tolerance before the test can be approved

	#2 http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/toDataURL.jpeg.quality.basic.html
	Is correct

	#3 http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/2d.missingargs.html
	Needs an update, maybe throw == pass, or need to wait till WebIDL progresses more on the expected exception

	#4 Minor - need to point images to another location, instead of http://excors.googlepages.com/yellow.png
	Just need to point to test2.w3.org rather than google

-Kris


Here is the IRC log from the meeting, trackbot issues so no fancy autogenerated notes.
*** krisk [836b004c@128.30.52.43] has joined #htmlt
*** krisk Ms2ger trackbot gsnedders @jgraham
*** Channel created on Sun Aug 15 01:32:28 2010
<Ms2ger> trackbot-ng, start telcon
<trackbot> Sorry... I don't know anything about this channel
<trackbot> If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)
*** Zakim [rrs-bridgg@128.30.52.169] has joined #htmlt
<krisk> zakim, this is htmlt
<Zakim> krisk, I see HTML_WG(HTMLT)11:00AM in the schedule but not yet started.  Perhaps you mean "this will be htmlt".
<Ms2ger> Zakim, this will be htmlt
<Zakim> ok, Ms2ger; I see HTML_WG(HTMLT)11:00AM scheduled to start in 1 minute
<krisk> ok we'll be more patient
<krisk> zakim, this is htmlt
<Zakim> krisk, I see HTML_WG(HTMLT)11:00AM in the schedule but not yet started.  Perhaps you mean "this will be htmlt".
<Ms2ger> Zakim, this will be htmlt
<Zakim> ok, Ms2ger; I see HTML_WG(HTMLT)11:00AM scheduled to start now
<krisk> trackbot-ng, start telcon
<trackbot> Sorry... I don't know anything about this channel
<trackbot> If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)
<krisk> zakim, this is htmlt
<Zakim> krisk, I see HTML_WG(HTMLT)11:00AM in the schedule but not yet started.  Perhaps you mean "this will be htmlt".
<krisk> zakim, this will be htmlt
<Zakim> ok, krisk; I see HTML_WG(HTMLT)11:00AM scheduled to start now
<Ms2ger> trackbot, prepare telcon
<trackbot> Sorry... I don't know anything about this channel
<trackbot> If you want to associate this channel with an existing Tracker, please say 'trackbot, associate this channel with #channel' (where #channel is the name of default channel for the group)
<krisk> Not sure why trackbot and the telcon is having issues
<krisk> I'll ping plh after the meeting to see if this can get resolved
<Zakim> HTML_WG(HTMLT)11:00AM has now started
<Zakim> +[Microsoft]
<krisk> zakim, Microsoft is me
<Zakim> +krisk; got it
<krisk> The conf call is up - incase anyone wants to dial in
<krisk> Ok lets get going - looks like it will be on IRC
<krisk> Agenda: http://lists.w3.org/Archives/Public/public-html-testsuite/2010Sep/0015.html
<krisk> #1 Check for any bugs on approved tests
<krisk> we have one - http://www.w3.org/Bugs/Public/show_bug.cgi?id=10632
<krisk> I assume folks will agree that video_008.htm was wrong
<Ms2ger> I just commented that I agree
<krisk> opera?
<Ms2ger> jgraham, yt?
* jgraham just got back to the heyboard :)
<jgraham> *keyboard
<jgraham> I believe I agree that test is wrong
<krisk> OK
<krisk> I also updated the test @ http://test.w3.org/html/tests/submission/Microsoft/video/video_008.htm
<krisk> How about this test gets approved so I can close the bugzilla bug
* Ms2ger needs to look at it some more
<Ms2ger> The bug can be closed without a replacement, no?
<krisk> better to make progress on video tests
<krisk> the update basically swapped out the result - which matches the spec changes
<krisk> Mozilla was seemed to be passionate about getting this test updated
<krisk> Ms2ger how much more time do you need to look at the test?
<krisk> jgraham - did you have any feedback on video_008.htm?
<jgraham> krisk: No, i don't think so
<jgraham> I looked earlier in the week to check that I agreed it is wrong
<krisk> ms2ger are you still on IRC?
<krisk> I also updated video-006.htm per simon pieter's feedback
<krisk> from http://lists.w3.org/Archives/Public/public-html-testsuite/2010Jun/0035.html
<jgraham> OK, I just looked at video_008 again, and I am not sure I follow the logic
<jgraham> Is it testing that if the video loads the media attribute must be right for the current environment?
<jgraham> I can't see the normative text in the spec to back up that behaviour
<jgraham> Oh, wait
<krisk> so you don't think that video should play and the onplay event should not fire?
<jgraham> It's in the resource selection algorithm
<jgraham> No it's fine, I wasn't sure where the spec actually asserted that the media attribute had an effect
<jgraham> But I see it now
<krisk> ok
<krisk> how about video_006.htm
<krisk> or would you rather have simon re-review the update from Opera?
<jgraham> I think Simon would be the right person to do it
<krisk> Ok - I'll resond back to the list and add him
<krisk> Moving on to Agenda item #2
<jgraham> (aside: why do these tests use document.write so much?)
<jgraham> I basically agree with Philip's comments about his tests
<krisk> Ok so for #1 he will change the tollerance?
<jgraham> I haven't checked #3 in WebIDL yet though
<jgraham> I guess we can ask him to
<krisk> let's do that
<krisk> movng on to #2
<krisk> jgraham did you get the correct URL?
<jgraham> Yes. I agree with Philip on this one that the spec doesn't permit type conversion
<jgraham> HTML5 says "For the purposes of these rules, an argument is considered to be a number if it is converted to an IDL double value by the rules for handling arguments of type any in the Web IDL specification"
<jgraham> And in section 4.1.1. any, WebIDL says that string input always becomes a DOMString
<krisk> OK
<krisk> Moving on to #3
<krisk> So the spec removed this exception
<krisk> Though I think it should throw something
<krisk> at lest then the web dev will know they are calling the api wrong
<jgraham> Right, I think Philip is right that WebIDL should define this
<jgraham> I also suspect he is right that it currently says to throw
<jgraham> Although I can't quite be certain of the derivation from the spec
<krisk> Until WebIDL gets more complete I think we should just expect a throw to occur
<jgraham> It is lsited as an open issue in WebIDL
<jgraham> *listed
<jgraham> I expect it will either not throw or end up throwing TypeError but it is hard to be sure
<jgraham> Since generally UAs are rather inconsistent with the wrong number of arguments
<krisk> Isn't that the whole point of the tests?
<krisk> and specs?
<jgraham> Well yes
<jgraham> But this clearly hasn't solidified out yet
<jgraham> Anyway, I am happy to approve the test if it matches what WebIDL currently says
<krisk> well it doesn't
<jgraham> Sure
<jgraham> It needs to be changed to match WebIDL
<jgraham> But as long as it does I don't think we should worry too much about the possibility of WebIDL changing
<jgraham> Except in the general way that we need a better system to deal with changes
<krisk> Let's have him  update the test - at some later date if WebIDL changes the test can get updated.
<krisk> Until then we'll not approve this test
<krisk> #4 minor updates to re-point the test image
<krisk> Once this is done I think that these tests can be approved
<jgraham> Sure
<krisk> Ok then to summerize
<krisk> #1 Needs to update tollerance
<krisk> #2 is correct
<krisk> #3 Need an update and more agreement
<krisk> #4 Just need to update the image location
<jgraham> That sounds about right
<krisk> That is the end of the agenda
<krisk> shall we adjourn?
<jgraham> Sure
<krisk> Ok meeting is over - I'll send note out to the list

-----Original Message-----
From: public-html-testsuite-request@w3.org [mailto:public-html-testsuite-request@w3.org] On Behalf Of Kris Krueger
Sent: Monday, September 20, 2010 6:08 PM
To: 'public-html-testsuite@w3.org'; Philip Taylor <pjt47@cam.ac.uk> (pjt47@cam.ac.uk)
Subject: HTML Testing Task Force Conf Call Agenda 9/21/2010

Agenda

#1 Check for any bugs on approved tests
#2 Approval for next 25 Phillip Taylor tests 

Note this set of tests has a few bugs listed below, which I suspect will take a while to discuss.

If you have other items you would like, please email me directly.

-Thanks!

IRC #HTMLT
Time 16:00-17:00 UTC (11:00am-12:00pm Boston local) Zakim Bridge +1.617.761.6200, conference 48658

Canvas Tests with Bugs
#1 http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/toDataURL.jpeg.quality.basic.html

This test uses a tolerance for pass/fail.
The spec doesn't guarantee that the pixel array from toDataURL will match across lossless images.

#2 http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/toDataURL.jpeg.quality.basic.html

'0.01' should be valid input.
Canvas Spec (http://www.w3.org/TR/html5/the-canvas-element.html)
"For the purposes of these rules, an argument is considered to be a number if it is converted to an IDL double value by the rules for handling arguments of type any in the Web IDL specification. 
[WEBIDL]".

"The WebIDL for converting an argument to double (http://dev.w3.org/2006/webapi/WebIDL/#es-double)
states that the first step is to compute ToNumber on the argument passed in, '0.01', which should be valid."

#3 http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/2d.missingargs.html

The assertion in the testcase is no longer exists in the HTML5 spec.  
The spec use to state that missing arguments should raise a NOT_SUPPORTED_ERR exception.
However, the latest version does not.

#4 Minor - need to point images to another location, instead of http://excors.googlepages.com/yellow.png

http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.reset.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.drawImage.image.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.drawImage.canvas.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.create.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.cross.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.canvas.timing.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.canvas.fillStyle.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.canvas.strokeStyle.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.image.fillStyle.html
http://test.w3.org/html/tests/submission/PhilipTaylor/canvas/security.pattern.image.strokeStyle.html
Received on Thursday, 30 September 2010 00:40:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 30 September 2010 00:40:31 GMT