RE: DOM, markup, and "dynamic html"
In IE4, we always maintain and surface a valid tree for all documents.
The tree is exposed flattened in a collection based on a pre-order
traversal of the tree. From any element, the parent element can be
accessed, as well as the ordinal position of the element in the
For valid HTML documents, the tree is unambigious. For invalid HTML
documents, we do our best to clean it up to create a valid tree.
As Todd mentions, you will be able to separate your scripts, style, and
content into separate files.
<LINK REL="stylesheet" HREF="myFile.css" TYPE="text/css">
content goes here
> From: Todd Fahrner[SMTP:email@example.com]
> Sent: Saturday, May 24, 1997 1:11 PM
> To: Joel N. Weber II; Scott Isaacs
> Cc: firstname.lastname@example.org
> Subject: Re: DOM, markup, and "dynamic html"
> At 3:49 PM -0400 5/24/1997, Joel N. Weber II wrote:
> > Maybe I'm misunderstanding something, but it looks to me like
> > dynamic HTML assumes the browser internally flattens out the HTML
> > tree. That would make implementing it difficult in a browser which
> > uses a tree structure internally.
> > >From what little I've seen of dynamic HTML, it looks to me like
> > impossible to get any two browsers to support it the same exact way.
> > And it doesn't look like it's going to downgrade gracefully either.
> I don't quite follow you here - probably my shaky grasp of
> issues. But as for graceful degradation - that's at the heart of my
> questions. I'd say that something degrades gracefully if you end up
> shipping only the parts of a document that the client - any client -
> make good sense of. If you can have totally generic HTML (no
> markup) in one file, CSS in another, and scripts in a third, I'd say
> hit the target. And it's looking to me like that's what we'll have in
> 4.0 browsers, with the exception of NS's markup-based solution to
> "dynamism". *yawn*
> Todd Fahrner