Bug 12835 - WebKit fails to even load the W3C/NIST DOM Conformance Test Suite
Summary: WebKit fails to even load the W3C/NIST DOM Conformance Test Suite
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Major
Assignee: Nobody
URL: http://www.w3.org/DOM/Test/#releases
Keywords: NeedsReduction
: 26400 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-20 22:24 PST by Robert Burns
Modified: 2016-04-05 15:19 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Burns 2007-02-20 22:24:30 PST 
WebKit fails to even load the W3C/NIST DOM Conformance Test Suite. I couldn't determine why. This works in Fireforx 1.5.0.9. I marked this as major since I think tracking down the problem may be simple and this has significant importance for tracking down other DOM issues.
Comment 1 Alexey Proskuryakov 2007-02-21 02:06:50 PST 
It would definitely be nice to make this page work, but please note that most of these tests are available in WebKit repository anyway (LayoutTests/dom).
Comment 2 Alexey Proskuryakov 2009-06-17 01:46:08 PDT 
*** Bug 26400 has been marked as a duplicate of this bug. ***
Comment 3 Mahesh Kulkarni 2011-06-16 21:28:10 PDT 
W3C tests use JSUnit framework for automation. JSUnit framework (jsunit.net) doesn't officially support webkit based browsers. I'm trying to dig into the issue, IMO, problem is with JSUnit framework. Talked to JSUnit author Edward Hieatt, as per him,


ext Edward Hieatt [edwardh@gmail.com]
Sent: Thursday, June 16, 2011 6:01 PM
To: Kulkarni Mahesh (Nokia-MP/Boston)
Cc:edward@jsunit.net

Hi,

JsUnit is no longer supported.  We suggest using Jasmine instead: http://pivotal.github.com/jasmine/

-----------------------------------------------------------------------

IMO JSUnit isn't the framework W3C should probably bet on. Any thoughts?
Comment 4 BJ Burg 2016-04-05 15:19:22 PDT 
With the availability of web-platform-tests, and many of those running in-tree, I don't think this bug is really relevant any more. Please re-open if you disagree, and provide steps to reproduce on a recent WebKit-based browser.