XSL Discrepancies in IE7

[byuhobbes85]

I have an HTML document, and then an XML document that is converted to the same HTML by an XSL stylesheet. This works beautifully in FireFox, and I was very excited to convert all of my content to XML. However, when I viewed the page in Internet Explorer I saw some differences. Here are the two pages -- the HTML version (

http://arclite.byu.edu/aww4moodle/chapter1/chapterGuide_test.html

) and the XML version (

http://arclite.byu.edu/aww4moodle/chapter1/test.xml).

The menus on the left use the CSS hover properties to generate the popup effect, although JavaScript is used to make it render correctly in Internet Explorer. Both versions render the same in FireFox. The HTML page renders the same in IE as it does in FF, but the XML page renders the menu differently. It is thinner and the popups do not work.

Now my question is if there are any known or documented issues with XSL and IE7. Does IE7 load things in a different order than FF with respect to XSL, HTML, JavaScript, and CSS?

Check it out and let me know. Thanks!

Dan Standage

 

[tsuji]

>Now my question is if there are any known or documented issues with XSL and IE7.
If there are any issues with ie7, they would be issues with ie6 alike. The menu does not open on ie6 neither. I don't think however it is an issue of xsl/ie or xsl/ff. The problem should be the cross-browser-readiness of the css and js.

 

[Miros]

To-spec CSS is known to fail on IE7, so yes, it's probably in the CSS.

 

[byuhobbes85]

Thanks for your replies, but I was able to figure it out. In my XSL stylesheet, I had not defined an output method. Once I added the <xslutput /> tag defining that the document was HTML, IE7 displayed it fine.

By the way, we decided not to go through the hassle of supporting IE6 in our pages, so the menus never functioned in IE6. However, now that the page includes the <xslutput /> tag, things work fine in IE7.

Thanks.