199921 - xsl transformation seems to ignore noscript tag

Status: RESOLVED DUPLICATE of bug 67899

(Core :: XSLT, defect)

Description

[Nikolay]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; .NET CLR 1.0.3705)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

I have a simple browser sniffing html page which detects if the user has 
switched off javascript/java. I use XSL to generate this browser sniffing html. 
If I don't use XSL then both IE and Mozilla behave the same. however if I use 
XSL then mozilla does something unexpected and redirects to #neither. I will 
attatch the .xml and .xsl files needed to reproduce the bug.

Reproducible: Always

Steps to Reproduce:
1.enable javascript in mozilla
2.enable java in mozilla
3.open the attached xml file with mozilla

Actual Results:  
the browser redirects to #neither rather then #bothjavascriptandjava

Expected Results:  
redirected to #bothjavascriptandjava

Comment 1

[Nikolay]

Attachment: the xsl file used

the xsl transformation file used

Comment 2

[Nikolay]

Attachment: the xml data to be opened

this is the xml data to be used as input to the xsl transformation

Comment 3

[Nikolay]

Attachment: testing to see if the files need to be downloaded

if this works you shouldn't need to download both files to run the xsl

Comment 4

[Nikolay]

Comment on attachment 118929 [details]
testing to see if the files need to be downloaded

tried to reference the xsl transformation directly from bugzilla but it didn't
work!

Comment 5

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

This is an interesting one. Normally the HTML-parser drops the <noscript>
content on the floor so that it doesn't even get into the contentmodel (which
means that this must be broken in XHTML too).

I think the best way to fix this is to move the responsibility of the redirect
to the <meta> (instead of as now let the sink/outputhandler deal) and then teach
<meta> to look at its parents for a <noscript> elements.

The scriptloader does something similar, although it looks for <noframe> and
<noembed> tags. We should probably have a generic function somewhere that checks
if a node in the tree has a "disabling parent", and use that for a whole bunch
of elements.

Comment 6

[Nikolay]

any chance this could be fixed for 1.4? its a pretty major BUG!

Comment 7

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

first hint for when a bug will be fixed is the target milestone (though this
often tends to be a bit optimistic target). I agree that this is a pretty bad
bug, but it is just too late to make it for 1.4 (at least IMHO)

Comment 8

[John Keiser (jkeiser)]

This *is* bug 67899, and is fixed by the patch for bug 77296.

*** This bug has been marked as a duplicate of 67899 ***