W3C home > Mailing lists > Public > public-test-infra@w3.org > October to December 2011

RE: Use of ES5 features in teatharness.js

From: Kris Krueger <krisk@microsoft.com>
Date: Mon, 31 Oct 2011 22:12:28 +0000
To: James Graham <jgraham@opera.com>, "public-html-testsuite@w3.org" <public-html-testsuite@w3.org>
CC: "public-test-infra@w3.org" <public-test-infra@w3.org>
Message-ID: <0A605FCDA3A4DC45A98B0DDD1C5351A7034C69CF@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com>
I am fine with this...

The normal practice that we have followed is that it's ok to use features as long as they are supported in all browsers.
For example the structured clone tests use workers, since all browsers supported this 'feature'.

Unless it's something that is specific to what you are specifically testing...

For example using onerror() should not be generally be used since it is not supported by all browsers.

-Kris

-----Original Message-----
From: James Graham [mailto:jgraham@opera.com] 
Sent: Monday, October 31, 2011 1:22 PM
To: public-html-testsuite@w3.org
Cc: public-test-infra@w3.org
Subject: Use of ES5 features in teatharness.js

Will anyone have a problem if we start using ES5 features in 
testharness.js? It will allow more precise testing of some WebIDL stuff. 
I think all browsers ship ES5 implementations these days so there 
shouldn't be a problem with compatibility.
Received on Monday, 31 October 2011 22:13:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 31 October 2011 22:13:04 GMT