This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
I assume that that's the line that instructs XSL to convert the document. Without it, the document is unlikely to be converted. Is that what's going on? I'm not sure I see what that has to do with browser compatibility.
Bear Bibeault wrote:I assume that that's the line that instructs XSL to convert the document. Without it, the document is unlikely to be converted.
It's the line that instructs XSLT to convert the document to HTML. Without it, the document will be converted to XML unless the document is "recognizably HTML", i.e. its root node is an <html> element. (That's a rough approximation of what the spec says.)
I guess I'm still kind of confused about what the real issue is. Is it that the XSL is not working as expected, or is it that the rendered HTML and script is not working correctly after the conversion?
If the former, I seem to recall that XSL is not automatically triggered in any browser but IE? But I could be completely wet as I left XSL back in 1998 (where I think it still belongs ).
Yeah, XSLT in the browser is definitely one of those "It seemed like a good idea at the time" architectures, and you don't hear much about it any more, but I do think that browsers other than IE were made to implement it quite a few years ago.
Of course what I'm thinking of is the architecture where you send an XML document to the browser, and that XML document has a processing-instruction at the beginning linking to an XSLT document which is supposed to be used to transform the XML document to HTML for the browser to display. But from what I've seen in this thread, I have no idea whether that's the concept being asked about.