442385 - FireFox XSLT transform removes the closing tag for IFrame

Status: RESOLVED INCOMPLETE

(Core :: XSLT, defect)

Description

[Prem]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR 1.1.4322; MS-RTC LM 8; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

In XSL I have some thing like

<iframe id="{concat($CntrlId,'_', $HelpControlCounter, '_Frame')}" frameborder="0" src="{$HelpFrameSrc}"></iframe>
<div> .... div contents ... </div>

when the transformation happens on FireFox; it gets rendered as

<iframe id="clt001_1_Frame" frameborder="0" src="http://msn.com" />
<div> .... div contents ... </div>

The closing tag </iframe> is removed and firefox puts a /> in place of it.
But this breaks everything. Any thing written after the iframe is not getting displayed bcos an iframe requires a closing tag.

since my page has <iframe id="clt001_1_Frame" frameborder="0" src="http://msn.com" /> <div>..... div contents ... </div> .. 
then my div is not getting displayed.
It would have been worked fine if XSL transform would have resulted in html like this 
<iframe id="clt001_1_Frame" frameborder="0" src="http://msn.com"></iframe> <div>..... div contents ... </div>
but since the closing end tag was replaced by a /> everything breaks.


Reproducible: Always

Steps to Reproduce:
the details are enough to repro .. 
just do a xslt transform on firefox for iframe and a div following that.
Actual Results:  
XSL tranformation in firefox removes the closing tag </iframe> and puts a /> in place of it.

Expected Results:  
XSL tranformation in firefox should not remove the closing tag </iframe> as this is a must required tag for iframe.

Comment 1

[Martin]

Attachment: Transform with iframe testcase

As reported, I think this bug should be closed WORKSFORME.

Unlike IE, which serialises the transform output and then sticks it through an HTML parser, Mozilla browsers operate on a tree for XSLT. Therefore which of two equivalent XML serialisations might be used for an element is irrelevant, as can be seen from the attatched test which Firefox will render correctly, but IE will not.

Unless the reporter is using the JS interfaces to transform to a text representation and then trying to parse that as HTML, can only presume his stylesheet is in error.

Please provide a testcase like the attached that Mozilla fails, and IE succeeds?

Comment 2

[Prem]

I just saw the test attached by Martin .. you can see the the bug there itself 
I can see it is like this <iframe src="http://www.mozilla.org/"/>	
<p>The frame is closed.</p>
and one can see that the text after Iframe is not getting displayed when page is opened on Firefox or IE.. I cannot see a text for <p>The frame is closed.</p> written after <iframe src="http://www.mozilla.org/"/>	
This would have been displayed only if it was rendered as <iframe src="http://www.mozilla.org/"> </iframe> <p>The frame is closed.</p>

If in XSL I have 
"<iframe src="{$HelpFrameSrc}"></iframe>
<p>The frame is closed.</p>"

Then Firefox XSLTProcessor transforms it to HTML as 
<iframe src="http://www.mozilla.org/"/>	
<p>The frame is closed.</p>

Due to this the text following the Iframe "The frame is closed is not getting displated".

This is a bug with FireFox XSLT transform ... If I do the transform in IE it works .. IE XSLT transform will render it as 
<iframe src="http://www.mozilla.org/"> </iframe> <p>The frame is closed.</p>
and there we are able to the text after the iframe.

(In reply to comment #1)
> Created an attachment (id=327269) [details]
> Transform with iframe testcase
> As reported, I think this bug should be closed WORKSFORME.
> Unlike IE, which serialises the transform output and then sticks it through an
> HTML parser, Mozilla browsers operate on a tree for XSLT. Therefore which of
> two equivalent XML serialisations might be used for an element is irrelevant,
> as can be seen from the attatched test which Firefox will render correctly, but
> IE will not.
> Unless the reporter is using the JS interfaces to transform to a text
> representation and then trying to parse that as HTML, can only presume his
> stylesheet is in error.
> Please provide a testcase like the attached that Mozilla fails, and IE
> succeeds?

Comment 3

[Samuel Sidler (old account; do not CC)]

1.9 bugs don't block 1.8 releases.

Comment 4

[Martijn Wargers (dead)]

Prem, could you perhaps attach a testcase that shows the bug?
Or perhaps give a page where the error can be seen?

Comment 5

[Mike Beltzner [:beltzner, not reading bugmail]]

Nominate for wanted when you've got a testcase / confirmation.

Comment 6

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

Erm, the XSLT engine doesn't do any serializations at all. It creates a DOM. I take it that you are somehow serializing that DOM using an XML serializer and see the <iframe ... /> instead of the <iframe ...></iframe> that you are expecting?

As it happens in XML  <foo></foo>  and  <foo/>  are equivalent. You are seeing exactly the rendering as you are expecting, no? With everything after the iframe being rendered as it should, no?

You say:
The closing tag </iframe> is removed and firefox puts a /> in place of it.
But this breaks everything. Any thing written after the iframe is not getting
displayed bcos an iframe requires a closing tag.

What do you mean "this breaks everything"? Can you please attach a testcase showing this. Clicking the attached testcase I see the "The frame is closed" just fine on the screen, just under the rendered mozilla.org website inside the iframe. Do you not?

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 8

[Sean Feng [:sefeng211]]

Olli, is this still relevant?

Comment 9

[Olli Pettay [:smaug][[e-mail]]]

More a peterv question.

Comment 10

[Hsin-Yi Tsai (she/her)[:hsinyi]]

Marking S3 to get this old issue out of un-triaged list, though I am not sure if this is still valid.

Comment 11

[Hsin-Yi Tsai (she/her)[:hsinyi]]

Various folks said WORKSFORME. Without getting more information from the reporter, it's hard to make a real progress.