299918 - transformToX without matching templates neither errors nor outputs text content of default template

Status: RESOLVED INVALID

(Core :: XSLT, defect)

Description

[alexander :surkov (:asurkov)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050530
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050530

When I pass DOM node to transformToX method of XSLTProcessor object then method
always returns empty document (document.documentElement is null). When I pass
DOM Document then method returns valid XML document.

Reproducible: Always

Comment 1

[Axel Hecht]

Could you provide a test case?

Comment 2

[alexander :surkov (:asurkov)]

Attachment: testcase xsl

Comment 3

[alexander :surkov (:asurkov)]

Attachment: testcase

save xsl on root of hard disc c:/ or change path of xsl in xul file.

Comment 4

[Boris Zbarsky [:bzbarsky]]

Well, with that testcase I see the issue...

Comment 5

[Axel Hecht]

This happens because the stylesheet doesn't match a single node, and thus not
a single element is produced.

I would expect that the default stylesheet do generate some text content for the
script tag content, but that's it, as we never add an element, that just ends
up in nirvana.

I wonder if we want to throw an error on that.

Comment 6

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Alexander: Could you test if this has been fixed now? The fix in bug 187620 should have taken care of this one too.

Comment 7

[alexander :surkov (:asurkov)]

Attachment: testcase2

(In reply to comment #6)
> Alexander: Could you test if this has been fixed now? The fix in bug 187620
> should have taken care of this one too.
> 

I changed a testcase, just run it. I guess problem is there.

Comment 8

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Could you attach a testcase that works right out of bugzilla, i.e. without requesting UniversalXPConnect

Comment 9

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

This is invalid. The reason that the default templates don't generate any text is that the only text in the document lives inside a <script> element. And the XUL parser doesn't generate text nodes for such text.

So what happens is that the template in the stylesheet never matches and so only the default rules are used. And since there is no text in the document the default templates generate no content at all.