Closed Bug 435816 Opened 18 years ago Closed 15 years ago

XSLT Transformation fails in unique ways depending on how the document is loaded

Categories

(Firefox :: General, defect)

defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: 0.fractalus, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-11-01])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 When loading from a local file, the documents presented in the URL presented load fine, and the XSL transform is performed(*) however when loaded from a webserver, an error is presented stating the XSLT stylsheet does not have the mimetype of text/xml * DTDs are ignored in XSLT transforms. Reproducible: Always Steps to Reproduce: Load an XML document such as this: <blobs><blob /> <blob color="green" /></blobs> tied to a DTD that defines a default value for an element (such as this: <!ELEMENT blob EMPTY> <!ATTLIST blob color CDATA "black">) and an XSLT Transform that makes use of that value such as this: <xsl:template match="blob"> The color of a blob is <xsl:value-of select="@color"></br> </xsl:template> Actual Results: On a local file: The color of a blob is <br/> The color of a blob is green<br/> on a remote file: The XSLT stylesheet given does not have an XML mimetype Expected Results: The color of a blob is black<br/> The color of a blob is green<br/> When rendered in IE, there are no problems. tested in Firefox, IE6 and IE7. Firefox always produces the wrong result.
The only way the browser knows the type of a resource is Content-Type HTTP header. Your HTTP server probably does not have MIME type mapping (*.xsl -> text/xml) set correctly, uses some default (like application/octet-stream, or text/plain), thus the XSLT processor does not know what to do. Regarding IE, it reads resource content to determine its type, that is why it works in IE. I think its WONTFIX.
This is a mass search for bugs that are in the Firefox General component, are UNCO, and have not been changed for 800 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the bug, please update this bug. If the issue is gone, please set the resolution to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.