Re: XSLT no longer display the transformed elements
Michael Vincent van Rantwijk <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.layout.xslt |
|---|---|
| Organization | Another Netscape Collabra Server User |
| Message-ID | <[email protected]> |
Martin Honnen wrote: > Note cross post and followup-to the xslt group. > > Michael Vincent van Rantwijk wrote: > >> I installed SeaMonkey build 2005103110 to fix another bug but now XSLT >> no longer displays the transformed documents, but all elements are >> inserted (I checked this with The DOM Inspector) so I presume that >> either something has changed or I ran into another bug. I narrowed down this regression/bug to the following versions: Build ID: 2005101305 works Build ID: 2005102015 fails but there are no other Windows builds in this time frame. > What exactly are you doing, how are you using XSLT? Do you have an XML > document with a processing instruction > <?xml-stylesheet type="text/xsl" href="stylesheet.xml"?> > referencing a stylesheet and you are loading the XML in a browser window? > Or do you use the XSLTProcessor with script? Yes, we use an XSLTProcessor. > And if elements are there in the DOM inspector but do not render as you > expect them to do then if for instance you want to create XHTML elements > make sure they have the proper element name (e.g. p) _and_ the proper > namespace (e.g. http://www.w3.org/1999/xhtml), if you want to create SVG > elements make sure they have the proper element name (e.g. svg) _and_ > the proper namespace (e.g. http://www.w3.org/2000/svg). All XHTML elements are inserted with the correct name space so that is not it. > But I am guessing,, how about providing some details on what you are > trying exactly when something fails to render? Load feed file, this load triggers our JS function that does the XSLT Transformation and all elements are inserted into the target document, just like before but now they are no longer visible/rendered. Michael