TransforMiiX needs output-method xhtml

NEW
Assigned to

Status

()

Core
XSLT
--
enhancement
15 years ago
8 years ago

People

(Reporter: Bernd Eckstein, Assigned: peterv)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

Mozilla won't parse any XSL-Stylesheets with output-method="xhtml" secified in
XSL 1.1

No big thing, but Sablotron, XALAN and XT have support for it, and it is good
for creating xhtml-compliant code used for backward comatibility


Reproducible: Always

Steps to Reproduce:
1. add xsl:output-method="xhtml" to your xsl-stylesheet
2. load


Actual Results:  
parsing-error

Expected Results:  
producing correct xhtml output

Comment 1

14 years ago
I don't see neither the XSLT1.0 nor the 1.1 nor the 2.0 specs specifying forwards 
compatible behaviour for 
<xsl:output method="foo">
There is no xhtml output method in http://www.w3.org/TR/xslt11/#output.
http://www.w3.org/TR/xslt20/#element-output has xhtml output, though.

We might argue that this is a sensible thing to do in fcp, but I'm not sure.

IMHO, both wontfix and rfe are ok. I don't think we should add xhtml output method
to the 1.0 processing, though, that's verboten.

Comment 2

14 years ago
xhtml output is just xml output, as far as our content generation is concerned,
we may just eat that.
Status: UNCONFIRMED → NEW
Ever confirmed: true
IMHO: We might want to always generate xhtml document-node for this output
method. For xml-mode we should decide based on the rootnode or the doctype,
which we currently don't do.
QA Contact: keith → xslt
You need to log in before you can comment on or make changes to this bug.