RESOLVED INVALID 11288
Rendered source not shown for xml/xslt files 
https://bugs.webkit.org/show_bug.cgi?id=11288
Summary Rendered source not shown for xml/xslt files
biz+webkit
Reported 2006-10-14 00:04:53 PDT
When an xml file is loaded containing an xml-stylesheet directive (client-side xml/xsl transformation), Drosera shows the xml file, but does not show nor allow the file-selection of the rendered HTML or javascript files included in the results of the transformation. The "pause" button works and will pause any javascript on the rendered page. However, if Step Into (etc) are used, Drosera highlights lines in the xml file, not the actual javascript. Note that Web Inspector shows the rendered DOM nodes correctly instead of the XML. For example (psuedo code, not tested): file.xml: <?xml version="1.0" encoding="ISO8859-1"?> <?xml-stylesheet type="text/xsl" href="file.xsl"?> <file> Lines so Drosera can point to one when Stepping into javascript . . . . . . . . . . . . . . </file> file.xsl: <xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output method="html" version="4.0" encoding="iso-8859-1" indent="yes"/> <xsl:template match="file"> <html lang="en"> <head> <title>XSLT Example</title> <script type="text/javascript" language="javascript"> function test(form) { alert("In Function"); return false; } </script> </head> <body> <a href="#" onclick="test()">Show Alert</a> </body> </html> </xsl:template> </xsl:transform>
Attachments
Add attachment proposed patch, testcase, etc.
Timothy Hatcher
Comment 1 2006-10-18 22:24:00 PDT
Interesting case. This will be tricky to fix I think.
biz+webkit
Comment 2 2007-05-12 23:02:48 PDT
Still doesn't work in revision=21432. As stated, sing the test files in the description, Web Inspector shows rendered HTML. Drosera only shows the XML and does not show the rendered HTML nor the javascript files in the file browser. Pausing and stepping will show the function name in the Drosera Function window, but will not show the javascript code.
Timothy Hatcher
Comment 3 2008-05-17 09:17:01 PDT
I suspect this might still be an issue in the new Web Inspector debugger.
Blaze Burg
Comment 4 2014-01-12 10:57:47 PST
This could still be an issue, but without a test case, we can't make any progress. Please re-open if it reproduces in a nightly, and include a standalone test case. Thanks!
Note You need to log in before you can comment on or make changes to this bug.