[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Public Comment
Comment from: elharo@metalab.unc.edu This may be a legal recoverable error, but it's pretty weird. In test case BVTs_bvt020 we find the following: <xsl:fallback xsl:exclude-result-prefixes="ns3"> <x/> </xsl:fallback> Note the use of xsl:exclude-result-prefixes on an element in the XSLT namespace. I think this is an error. The spec only allows xsl:exclude-result-prefixes on literal result elements. Should this be exclude-result-prefixes instead? I suspect processors are allowed to recover from this error after signalling; but Xalan-J doesn't and it's still weird.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]