OK, for anyone interested, I eventually traced down the problem.
Internet Explorer (MSXML) cannot handle the following template. And
now I have another question.
<xsl:template match="HtmlAttribute">
<xsl:attribute name="@name"><xsl:value-of select="text()"/></xsl:attribute>
</xsl:template>
So is this a bug in MSXML?
I have run this through 3 other processors and none of them complained
about the above template. See the error IE gives in my original post
below.
BTW. to uncover this, I had to poke and prod with NUMEROUS commenting
outs to track down the problem. OK, this is normal for a developer
(sometimes), but IE is a huge pain because it does not read the
stylesheet changes unless you exit all instances of IE and start it up
again. I had to do this each time I commented something out to test
it. Furthermore, it STILL says "the XML source is unavailable for
viewing". As far as I am concerned, this is a REAL WORLD issue and
weighs heavily against IE in the XML/XSLT development stakes if one
wants to evaluate and compare browser platforms - I don't care how
inferior Transformiix is supposed to be under certain conditions, at
least I don't have to restart Mozilla for every single code change.
Anyway, I think the code above has shown MSXML to have a bug when
Transformiix does not. So it's 6 of one, half a dozen of the other.
They both have shortcomings. One allows you to develop with it - in
business time speeds.
I'm not sure how I'm gonna work around this bug. I need this functionality :/
On 10/02/06, Terence Kearns
<terence(_dot_)kearns(_at_)canberra(_dot_)edu(_dot_)au> wrote:
Unfortunately there are still some traditionalists out there who
insist on using IE. So far, my web application is only working in
Firefox. I load it up in IE, and I just get a lame error with no line
number and "the source is unavailable". Honestly, I don't know how
people put up with developing apps exclusively under IE. It's like
having both arms and legs chopped off once you've developed with FF.
IE says "This name may not contain the '@' character: -->@<--name
Error occurred during compilation of included or imported sty..."
My server-side transform processor doesn't compain about any errors
either so I'm assuming it's not just FF being lenient. I don't want to
transform server-side unless I absolutely have to.
Surely there must be some sort of extension that you can get for IE
that allows you to debug with it.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--