I have now generated a new implementation report [1] to go with the
updated testsuite.
As I detailed previously on public-webapps-testsuite [2], the new tests
use testharness.js and, as a result, some of the tests which passed
under the old framework now fail in some browsers. This is mostly
because the new tests explicitly check for TypeError on the 'no
parameter' tests, whereas the old tests accepted any exception as a pass.
WebKit is also failing one of the :target selector tests, probably
releated to the way the test loads the testing page in an iframe.
[1]
http://dev.w3.org/2006/webapi/selectors-api-testsuite/level1-baseline-report.html
[2]
http://lists.w3.org/Archives/Public/public-webapps-testsuite/2012Jun/0009.html
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
