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

RE: Test Case Approval Request

From: Kris Krueger <krisk@microsoft.com>
Date: Tue, 20 Apr 2010 06:20:18 +0000
To: Anne van Kesteren <annevk@opera.com>
CC: "public-html-testsuite@w3.org" <public-html-testsuite@w3.org>
Message-ID: <FA9085650D2F8B4A9D501ED9D9706E9A05F4E4@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Just to make sure I understand your feedback...

You think that the test is valid and can help overall browser interoperability looking at past browser implementations.
Though the title of the test needs to be more clear, call out that it's a content attribute test rather than an interface test.

-Kris

-----Original Message-----
From: Anne van Kesteren [mailto:annevk@opera.com] 
Sent: Monday, April 19, 2010 10:53 PM
To: Kris Krueger
Cc: public-html-testsuite@w3.org
Subject: Re: Test Case Approval Request

On Tue, 20 Apr 2010 10:43:26 +0900, Kris Krueger <krisk@microsoft.com>  
wrote:
> OK - I submitted an interface test for the HTMLAnchorElement
> See ->  
> http://dvcs.w3.org/hg/html/raw-file/tip/tests/submission/Microsoft/interface/anchor_href.htm

>
> This is quite a simple framework and removes all the old harness code  
> except for the assert functions.
>
> One question would be would we rather have all the attributes tested on  
> one page (href, target, rel, etc...) or have one page for each attribute.

I haven't really looked at the framework in use, but this test is not  
testing the href IDL attribute. It is testing that the href content  
attribute behaves like any other content attribute. I suppose that is  
somewhat valuable given how Opera treated certain content attributes and  
how Internet Explorer treated IDL and content attributes the same, but it  
is certainly not testing the interface.


-- 
Anne van Kesteren
http://annevankesteren.nl/


Received on Tuesday, 20 April 2010 06:21:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 20 April 2010 06:21:05 GMT