Re: IE5 and XML (was) Re: books & mozilla

> The XML itself is not the problem, but the only real way to *present*
> XML-formatted data in both browsers is using style sheets (which means
that
> you can't change the order the data elements are in, just make them look
> nice).

However, as you have wisely started to point out, direct styling is of
virtually no use for most
XML structures. Those structures for which it is of great use are
renderingML in anycase, such as SVG and XHTML.

JavaScript and the DOM API is the only way to transform XML on the client
for both these browsers. This is a far superior system than XSLT in anycase,
even MSXSL 'improvements' ape the functionality of a programming language
(eval, as previously indicated).
There isn't really any cross-browser conflict it the DOM, bar the fact that
both browsers currently have bugs in their implementation of the DOM. It's a
very far cry from the nightmare of  version 4 DHTML :)


----- Original Message -----
From: "Peter-Paul Koch" <ppk(at)xs4all.nl>
To: <hwg-xml(at)hwg.org>
Sent: Wednesday, April 26, 2000 6:57 AM
Subject: Re: IE5 and XML (was) Re: books & mozilla


> >Sooooo, Microsoft made some best
> >guesses of what it would be (or how they wanted it to be) and ran with
> >that in releasing 5.0.
>
> Yep. They also made it support a proprietary XSL (xsl:eval, for instance,
> is IE only).
>
> I've also read that the differences between IE and
> >Netscape implementation of XML will continue the problems with cross
> >browser compatibility.
>
> The XML itself is not the problem, but the only real way to *present*
> XML-formatted data in both browsers is using style sheets (which means
that
> you can't change the order the data elements are in, just make them look
> nice).
>
> Netscape 6 doesn't support XSL. Maybe JavaScript would be a solution. Has
> anyone tried using JavaScript to transfer XML to HTML? Theoretically it
> should be possible in both IE5 and NN6.
>
> ppk
>

HWG hwg-xml mailing list archives, maintained by Webmasters