Level 1 DOM Tests

[Oisín Grehan]

Hi,

I've just finished writing a head-wrecking webapp for Gateway. It will
be going live pretty soon - it's a DHTML app that reads in legacy
machine component CSV data files from an AS/400 system and allows
customers to customize their base desktop machines with additional
components. It works with both Netscape 4 and IE4 with an identical GUI.
It was about four months of torture trying to get Netscape to work even
halfway like IE's completely superior layout engine. I'd be quite
interested in testing Mozilla's 5 new engine. I'd consider myself pretty
much well versed in x-platform development html/javascript at this stage
- I found myself quite enjoying working around Netscape's spontaneous
crashing and inept and completely disfunctional "layer technology". I
feel by helping to get Mozilla 5.0 up to IEs standard I'd be doing
everyone a favour.. :)

Regards,

- Oisin Grehan
Technical Manager
Labyrinth Solutions
p. +353-1-6624976 f. +353-1-6624978

[Angus Davis]

Oisín Grehan wrote:

> I feel by helping to get Mozilla 5.0 up to IEs standard I'd be doing
> everyone a favour.. :)

First and foremost, understand that while IE4 undoubtedly has some cool
technologies in it, we're shooting for full compliance with the W3C's DOM
Level 1 (Core and HTML) standards in NGLayout. IE4's APIs are no less
proprietary than those in Nav 4.

To get started writing test cases and demo content, have a look at
http://www.w3.org/TR/REC-DOM-Level-1 .

There are two big feature areas not covered by this spec:

1. CSS object model
2. Events

I'll work on getting something published to our mozilla.org pages that gives
an overview of our APIs here. Here's a brief overview:

Changes to inline styles on all elements should be working today, like this:

<p onmouseover="this.style.color='red'">foo</p>

You can get the relevent element.style.foo property by taking the name of
the CSS1/2 property, removing the dash, and camel casing it. e.g.
font-family --> fontFamily; letter-spacing --> letterSpacing; etc.

For events, you can use HTML attributes in the tag (e.g. <p
onmouseover="...">) or you can do it from JavaScript. Here's an example that
puts a onMouseOver event handler on every link in the document (note this
script should be called after the document has completed loading):

function handleIt(e) {
// keyword "this" refers to the element that fired the event
// variable "e" refers to the event that was fired
this.style.color="red";
}

var as = document.getElementsByTagName("A");
for (var i=0; i<as.length; i++) {
as[i].onmouseover=handleIt;
}

Note that in the future, Action Sheets will make this easier.

Obviously this is a gross oversimplification, but hopefully it's enough to
get you started doing something useful. Please post the URLs here for
anything cool you create - your help is appreciated.
-angus

[Angus Davis]

Please post a URL for your stress tests whenever they're ready. Thanks,
-angus

Marc Bonnier wrote:

> Hi, you want to stress the browser I may have a good project for that
> purpose.
>
> I'm near the release of an object inspector written 100% in JS & HTML. It
> is 16000 lines of code - fully object oriented. This alone is a good test
> for a browser.
> ...