Closed
Bug 296391
Opened 20 years ago
Closed 8 years ago
Pass W3C ECMAScript DOM Conformance Test Suites
Categories
(Core Graveyard :: Tracking, defect)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: jmdesp, Unassigned)
References
()
Details
(Keywords: helpwanted, meta)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.8b2) Gecko/20050527 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.8b2) Gecko/20050527 On the page http://www.w3.org/DOM/Test/, W3C has a list of test suits to check ECMA/DOM support for : - Level 1 Core - Level 2 Core - Level 2 HTML etc We pass most of the tests, but even for level 1 a few fail. There are several hundreds ot test, so the conformance testing must be very inclusive. This should be a tracker bug, with separate bug opened for the specifics issues that cause the tests to fail. Several of them are probably already in bugzilla. Reproducible: Always Steps to Reproduce:
Comment 1•20 years ago
|
||
Once you no longer need this tracker bug, please close it. Thanks.
Comment 2•19 years ago
|
||
I suggest filing bugs on specific tests we fail and having them block this one (and ccing DOM owners on said bugs).
Comment 3•19 years ago
|
||
*** Bug 336670 has been marked as a duplicate of this bug. ***
| Reporter | ||
Comment 4•19 years ago
|
||
A part of the work that needs to be done (identifying specific problems, opening bug as required for them) has been done in bug 125665 for DOM 1. DOM 1 certainly is the priority, but there could be very minor issues in DOM 1 that are less important than some really interesting new thing form DOM 2, etc. I update the status of this bug to reflect the fact that anybody who actually has the time to do that should feel free to appropriate it.
Comment 5•19 years ago
|
||
*** Bug 336816 has been marked as a duplicate of this bug. ***
Comment 6•16 years ago
|
||
I've run DOM 2 HTML test on Fx trunk. Errors and failures are listed here: http://pazziaumana.netsons.org/dom2-err-fx3.html I noticed 3 big problems: 1) there's a regression from Fx2. This error is displayed only on trunk: 2. http://www.w3.org/2004/04/ecmascript/level2/html/HTMLAppletElement11.html:HTMLAppletElement11 failed "object" Expected DOMTSApplet.dat (string) but was http://www.w3.org/2004/04/ecmascript/level2/html/files/DOMTSApplet.dat (string) Stack trace follows: > JsUnitException > _assert > assertEquals > HTMLAppletElement11 2) there's a considerable slowdown. Fx3 takes 1780 seconds to run the entire test, Fx2 only 646. I don't know exactly what causes the slowdown. 3) the log message of the 10th error is different. On Fx2 is: Expected ./pix/logo.gif (string) but was http://www.w3.org/2004/04/ecmascript/level2/html/files/pix/logo.gif (string) on the contrary on Fx3 is: Expected ./pix/logo.gif (string) but was http://xw2k.sdct.itl.nist.gov/brady/dom/pix/logo.gif (string)
Comment 7•13 years ago
|
||
WONTFIX? These tests are unlikely to be relevant at this point.
Comment 8•8 years ago
|
||
Marking all tracking bugs which haven't been updated since 2014 as INCOMPLETE. If this bug is still relevant, please reopen it and move it into a bugzilla component related to the work being tracked. The Core: Tracking component will no longer be used.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•