Slashdot Mirror


W3C DOM Level 1 Conformance Test Suite Released

Dimitris Dimitriadis of Ontologicon , W3C Representative to the DOM Test Suite Group, writes with an announcement also signed by Philippe Le Hégaret, W3C DOM Activity lead, and Mary Brady of NIST: "The DOM Test Suite Group releases the first version of the DOM Conformance Test Suite, Level 1 Core. The first version of the DOM Conformance Test Suite for Level 1 Core has been released by the DOM Test Suite Group. The DOM TS aims at helping implementors test their implementations' conformance with the W3C DOM Level 1 specification. This work, launched by W3C and NIST, is a publically developed and open framework to test the DOM Level 1 Core implementations. Read about the Document Object Model (DOM) Conformance Test Suites at http://www.w3.org/DOM/Test, where you can also download the DOM TS distribution. Comments are appreciated and need to be sent to www-dom-ts@w3.org (online archive at http://lists.w3.org/Archives/Public/www-dom-ts)."

10 comments

  1. Karma Suicide! by jeffy124 · · Score: -1, Offtopic

    After 600+ posts and 20 articles, my karma has been peaked at 50 for what seems like forever now. My new campaign: Karma Suicide!! Every post from now until my karma's back at zero will be this short crapflood posted with my +1 bonus (which i've lost already). So moderators: Do your worst! You got only 9 more points to go! Mod me troll/OT/Overrated/etc to get my karma back to where it began. Do this ASAP! And as for the rest of you, commit karma suicide today!

    --
    The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
  2. Is anyone actually implementing DOMs anymore? by Anonymous Coward · · Score: 0

    I'm sure there are a few implementations out there, but does any of them have any significant benefit over another?

    1. Re:Is anyone actually implementing DOMs anymore? by Anonymous Coward · · Score: 0
      Technological benefits? No... not really. They're all pretty much the same.

      The W3 one has the w3 name behind it, that's all. I'll be using this when it's well supported in Mozilla (personally I haven't been able to fault Mozilla's handling of DOM1 but I haven't tried anything difficult so I guess my experiences don't count for much).

  3. Kathleen !worth good spelling or grammar. by Anonymous Coward · · Score: -1, Offtopic
    Kathleen !worth good spelling or grammar.

    Kathleen, I wanted to do this in this most potentially embarassing way possible, and I figured doing it here and now, in front of a quarter of a million strangers was as good a way as any. I love you more then I can describe within the limits of this tiny little story. We've been together for many years now, and I've known for most of that time that I wanted to spend my life with you. Enough rambling. Will you marry me?

    Embarrassing. Double 'r', double 's'.

    I also disagree with your use of then. Than is used to be comparative. Then is indicative of expressions of time or timing and consequence.

    It's wiser being good than bad; It's safer being meek than fierce; It's fitter being sane than mad. --R. Browning.

    Might I suggest a more heartfelt and serious way of proposal? What was the diamond on the ring? A penguin shaped imperfect piece of shit bought at the mall last minute? Zales? I doubt Mr. JUBEI machine knows an SI-J from a VVS1-E. You are very heavily 'included,' Malda. Can you think of s shittier and more cliché day to propose, or is Valentine's Day king shit of that Tird Island. She must be a lobotomized retard, otherwise you should have spat upon by your would be spouse.

    Hey, loserboi, don't forget to invite Larry Wall to the wedding and write your vows in a Perl Script. Then you can "chomp" down on your cake.

    You don't have to be a Kreskin to see the end of this loser elopement ending in the very near future.

    This is crap, Malda. If I was an English teacher, and this was a 5 grader's half assed attempt at writing a romantic short story, I'd throw the script back in the kid's face and wonder who dropped him as a kid. This is pathetic. I feel bad for your wife.

    1. Re:Kathleen !worth good spelling or grammar. by Anonymous Coward · · Score: -1, Offtopic
      Embarrassing. Double 'r', double 's'.

      I also disagree with your use of then. Than is used to be comparative. Then is indicative of expressions of time or timing and consequence.

      It's wiser being good than bad; It's safer being meek than fierce; It's fitter being sane than mad. --R. Browning.

      Might I suggest a more heartfelt and serious way of proposal? [bit late now, don't you think?] What was the diamond on the ring? A penguin shaped [compound adjective. Hyphenate: penguin-shaped] imperfect piece of shit bought at the mall last minute? Zales? I doubt Mr. JUBEI [cmdrtaco.net] machine knows an SI-J from a VVS1-E. You are very heavily 'included,' Malda. Can you think of s shittier and more cliché [the adjective is cliched. Consider losing the accent on the e. It looks a bit pretentious] day to propose, or is Valentine's Day king shit of that Tird Island. She must be a lobotomized retard, otherwise you should have spat upon by [this makes no sense] your would be [would-be] spouse.

      Hey, loserboi, don't forget to invite Larry Wall to the wedding and write your vows in a Perl Script. Then you can "chomp" down on your cake.

      You don't have to be a Kreskin to see the end of this loser elopement ending [one of these ends is redundant] in the very near future.

      This is crap, Malda. If I was [were. subjunctive mood] an English teacher [*snort*], and this was [were again] a 5 [adjective is fifth] grader's half assed [half-assed] attempt at writing a romantic short story, I'd throw the script back in the kid's face [use a pronoun: his] and wonder who dropped him as a kid [but he already is a kid]. This is pathetic. I feel bad for your wife. [fuck you]

  4. IE is way more compatible than Mozilla? by svu · · Score: 1, Informative

    Just tested ECMAScript on Mozilla 0.9.8. I got 25 failures and 63 errors out of 290 runs! It is not very good, isn't it? IE6 gives 18 failures and 10 errors. Really sad... Hope mozilla.org will do something about it...

    1. Re:IE is way more compatible than Mozilla? by Shimbo · · Score: 1

      Just tested ECMAScript on Mozilla 0.9.8. I got 25 failures and 63 errors out of 290 runs! It is not very good, isn't it? IE6 gives 18 failures and 10 errors. Really sad...


      Well that's one way of looking at it. Support for the DOM in IE has been pretty good for a while; it's just that they didn't draw attention to it by dropping their proprietary DOM. CSS on the other hand...


      However, if IE/Mozilla/Opera/etc. are competing to get these errors down then everyone wins. It's a virtuous circle; I'm mildly optimistic about the web when I see vendors compete to improve support for standard features.


      Yes, it's slightly sad for Mozilla that it lags in these tests. However, it's good for everyone in the long run if there are independent tests published and people care about the results.


      It's not a zero sum game. Better standard support in IE makes it easier for developers to write corss-platform code.

    2. Re:IE is way more compatible than Mozilla? by Anonymous Coward · · Score: 1, Informative

      For what its worth,
      I tested todays mozilla build (2-15)
      and it only has 19 failures and 58 errors,
      so IE and Moz are quickly converging.
      I'm willing to bet that the next IE release
      and mozilla 1.0 will both have 0 failures, 0 warnings.

  5. Of course they will... by ringbarer · · Score: -1

    They'll sit around and whine about it before spouting more FUD that Mozilla doesn't support MS-HTML.

    Then they'll debut their new and improved scripting interface that breaks all previous third-party plugin code written for Mozilla, but at least you can write your mouseovers in INTERCAL now. w00t!

    FOUR YEARS and they STILL don't have a stable API.

    Mozilla is regarded with laughter and derision by any REAL computer users. You know, those people that USE computers rather than worship them.

    --
    "Why did they cancel my favorite Sci-Fi show? I downloaded ALL the episodes!"
  6. More complicated than just counting failed tests by CArnold · · Score: 2, Insightful

    Were you never warned not to compare apples and oranges. The raw test failure count is not a good metric (unless it is zero). Several points: 1) The DOM L1 test suite currently only contains tests that exercise the XML and SVG implementations and contains no HTML tests. For MS IE, this means testing whatever is loaded to MSXML2.DomDocument or the Adobe SVG control. For Mozilla, this means the internal XML DOM implementation. We are awaiting submission of additional tests that will test HTML implementations of DOM L1. 2) Many of the Mozilla test failures are due to Mozilla not parsing the DTD and providing default values for attributes. 3) This is the first of several test suites for different levels and modules of the DOM. Don't be making conclusions just on the basis of the L1 DOM Core suite. 4) Exceptions throw to the JScript binding from MSXML do not adhere to the DOMException interface (from the public documentation for Windows Scripting, it does not appear possible to craft the exception class that is generated for a COM failure HRESULT). The test adapter for MSXML compensates for this. The compensation is justified by the third paragraph in http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/ level-one-core.html#ID-17189187 which allows for the limitation of object system. If this compensation is eliminated, then MSXML will fail every test that checks the code for an exception which will radically change the raw numbers (find MSXMLDocumentBuilder_isDOMExceptionCode(ex, code) in DOMTestSuite.js and add "return (ex.code == code);" in case you are curious.) So, don't compare apples to oranges, don't rely on default attribute values for Mozilla's XML DOM and don't rely on DOMException.code on MSXML. p.s. I've participated in the DOM Test Suite work, but the opinions expressed in this message are my personal opinions and not that of the DOM Test Suite group or any other group of the W3C. p.s.s. A unofficial superficial analysis of the test failures for an earlier version of Mozilla against an working draft versions is available at http://lists.w3.org/Archives/Public/www-dom-ts/200 1Nov/0011.html