Re: still too early for XHTML :-((

We've been using XHTML+XMLC for 9 months, and we too encountered that
problem.  My solution, was to do it this way:
<script src="x"><!-- IE Sucks --></script>

every place we want to use a "self-terminating script tag".

Having said that, I'm also curious as to what the document type you're
sending down in your request headers.  Even though we produce XHTML, we're
really telling it we are an html document.  It's quite possible that
sending the correct "Content-type" header down will work.  Problem is, I
don't know what the correct type REALLY is.

> Hi,
>
> as you may recall from my occassional posts here, I have been trying to
> use XHTML with Enhydra for several months already. I patched various
> things in Enhydra/XMLC (some fixes, some hacks) in order to get it
> working and was almost happy - until I decided to try also non-Gecko
> browsers. After some hours of debugging IE6 problems I managed to
> isolate a possible bug in SCRIPT tag handling:
>
> http://www.prevue.cz/ie6bug.html
>
> For me it seems as a clear evidence that I wasted my time on the XHTML
> for nothing. If the latest browser with 95% market share is unable to
> load javascript file then XHTML is completely unusable.
>
> I don't think XMLC/Enhydra would be modified in the way it outputs the
> SCRIPT tag just to fix this buggy behaviour of IE. Or am I wrong and
> such patch would be accepted in the mainline?
>
> Anyway, I'll most probably convert my XHTML files to HTML, change the
> XMLC parser back to the default one and be happy again.
>
> Petr
>
>
> _______________________________________________
> XMLC mailing list
> XMLC@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc