10462 2006-08-17 10:54:53 -0700 XMLHttpRequest does not respect xml-stylesheet 2006-11-12 02:57:25 -0800 1 1 1 Unclassified WebKit XML 420+ Mac (PowerPC) OS X 10.4 RESOLVED INVALID P2 Normal --- 1 jake.devine webkit-unassigned ap oldest_to_newest 52840 0 jake.devine 2006-08-17 10:54:53 -0700 The XML Document returned is original, untransformed, document at the location specified by the URL. It doesn't look like I can attach files to this bug, but I'll give you a quick example: xmldoc.xml: -------------- <?xml version="1.0" encoding="UTF-8" ?> <?xml-stylesheet type="text/xsl" href="xsldoc.xsl"?> <page> <paragraph> <line>This is line one.</line> <line>This is line two.</line> </paragraph> </page> xsldoc.xsl: -------------- <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text" omit-xml-declaration="yes" /> <xsl:template match="//page"> <xsl:for-each select="paragraph"> <p> <xsl:apply-templates /> </p> </xsl:template> <xsl:template match="line"> <br> <xsl:value-of select="."/> </br> </xsl:template> </xsl:stylesheet> ------- When I enter the url for xmldoc.xml into the browser, i get the result of the transformation, however requesting it in an XMLHttpRequest just returns xmldoc.xml as an xml document. 52843 1 10096 jake.devine 2006-08-17 11:35:05 -0700 Created attachment 10096 The XML document listed in the description. 52845 2 10098 jake.devine 2006-08-17 11:35:56 -0700 Created attachment 10098 The XSL document listed in the description (There were typos in the listing that are corrected here) 52883 3 hyatt 2006-08-17 16:13:30 -0700 I didn't think transforms would be auto-applied to XMLHttpRequests. Does Firefox respect this? 52884 4 hyatt 2006-08-17 16:14:47 -0700 It's not clear to me that we should respect this.... since I would think you'd want the source doc rather than the result doc (XSL can transform you to plain text or HTML as well, and that seems really strange to me if you could get that kind of transformed result from XMLHttpRequest). 52885 5 jake.devine 2006-08-17 16:33:01 -0700 Firefox doesn't support this, unfortunately. Your recent addition of the XSLT processor makes this sort of moot (and hooray!), but I was just trying to work around the absence of browser-side transformations. I don't think that it would be totally unexpected behaviour, however. XMLHttpRequest already handles both text and XML data in response*, so either of those output methods could be interpreted. In any case, I can certainly appreciate not breaking compatibility with Mozilla in this regard, and since browser side XSL is in the nightlies, it's certainly nothing important. 45958 6 ap 2006-11-12 02:57:25 -0800 Closing as invalid per comments 4 and 5. 10096 2006-08-17 11:35:05 -0700 2006-08-17 16:01:16 -0700 The XML document listed in the description. xmldoc.xml application/xml 207 jake.devine PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiID8+DQo8P3htbC1zdHlsZXNoZWV0 IHR5cGU9InRleHQveHNsIiBocmVmPSJ4c2xkb2MueHNsIj8+DQo8cGFnZT4NCgk8cGFyYWdyYXBo Pg0KCQk8bGluZT5UaGlzIGlzIGxpbmUgb25lLjwvbGluZT4NCgkJPGxpbmU+VGhpcyBpcyBsaW5l IHR3by48L2xpbmU+DQoJPC9wYXJhZ3JhcGg+DQo8L3BhZ2U+ 10098 2006-08-17 11:35:56 -0700 2006-08-17 16:01:42 -0700 The XSL document listed in the description (There were typos in the listing that are corrected here) xsldoc.xsl application/xml 456 jake.devine PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjx4c2w6c3R5bGVzaGVldCB2 ZXJzaW9uPSIxLjAiIHhtbG5zOnhzbD0iaHR0cDovL3d3dy53My5vcmcvMTk5OS9YU0wvVHJhbnNm b3JtIj4NCgk8eHNsOm91dHB1dCBtZXRob2Q9InRleHQiIG9taXQteG1sLWRlY2xhcmF0aW9uPSJ5 ZXMiIC8+DQoJDQoJPHhzbDp0ZW1wbGF0ZSBtYXRjaD0iLy9wYWdlIj4NCgkJPHhzbDpmb3ItZWFj aCBzZWxlY3Q9InBhcmFncmFwaCI+DQoJCQk8cD4gICAgICANCgkJCQk8eHNsOmFwcGx5LXRlbXBs YXRlcyAvPg0KCQkJPC9wPg0KCQk8L3hzbDpmb3ItZWFjaD4NCgk8L3hzbDp0ZW1wbGF0ZT4NCgkN Cgk8eHNsOnRlbXBsYXRlIG1hdGNoPSJsaW5lIj4NCgkJPGJyPg0KCQkJPHhzbDp2YWx1ZS1vZiBz ZWxlY3Q9Ii4iLz4NCgkJPC9icj4NCgk8L3hzbDp0ZW1wbGF0ZT4NCjwveHNsOnN0eWxlc2hlZXQ+