Closed
Bug 319883
Opened 19 years ago
Closed 19 years ago
xsl transformation does not display properly
Categories
(Core :: XSLT, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: sqwyz, Assigned: peterv)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
2.13 KB,
application/xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; fr; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; fr; rv:1.8) Gecko/20051111 Firefox/1.5
Xls transformation does not display new elements in a new line.
For example, the <p></p> element is on the same line thant the <h1></h1> preceeding element.
The URL given above contains an exmple. If you replace le last extension ".xml" by ".php", you obtain the result when it's transformed server-side.
Reproducible: Always
Steps to Reproduce:
1.Display an XML file linked to an XSL Style Sheet that transform the XML into a XHTML file. This XHTML file is linked to a CSS style Sheet to style the document.
Actual Results:
The way firefox display the result do not seems correct : all is displayed as a single line.
Expected Results:
I expect each new block element to be displayed in a new line.
When I use a server side transformation or internet explorer it works as I expect.
Comment 1•19 years ago
|
||
The problem is that your transformation is outputing <h1> and other tags without any namespace. The output XHTML has <h1 xmlns="">...</h1> which is not a valid xhtml h1 tag.
If you change your XSLT to include the xhtml namespace, you get the output you expect. I'll add an attachment for the altered XSL file with some comments.
Comment 2•19 years ago
|
||
This it the altered XSL that writes out the tags with the XHTML namespace.
Assignee: nobody → peterv
Component: General → XSLT
Product: Firefox → Core
QA Contact: general → keith
Version: unspecified → 1.8 Branch
Looks like this was invalid and has now been fixed in the application
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•