276206 - </noscript> closing <DIV>

Status: RESOLVED INVALID

(Core :: DOM: HTML Parser, defect)

Description

[cohenlaur]

Hello Firefox team,

I am building a web site using javascript, and I want the users who do not have
javascript enabled to get a <DIV> with one format and the ones having javascript
to get a <DIV> with another format.

The code I have written is woking :
- perfectly with IE6 with javascript enabled
- perfectly with IE6 without javascript enabled
- fairly with OPERA with javascript enabled
- fairly with OPERA without javascript enabled
- perfectly with Mozilla with javascript enabled
- not at all with Mozilla without javascript enabled

You can take these small lines for testing when JS is not enabled:
                                           ^^^^^^^^^^^^^^^^^^^^^^
quote
++++++++++++ <SCRIPT> ++++++++++++++++
<noscript>
	<div id="normal">
	Toto
</noscript>
Titi
</div>
++++++++++++ <CSS> +++++++++++++++
div#normal {
font-family:verdana, sans-serif;
font-size: 100%; 
width: 100%;
height:100%;
color:navy;
margin-left:200px;
background:url("../Backgrounds/Pan_Gauche2.gif") no-repeat fixed;
background-position:0 -55px;
padding:30 10 0 10px;
}
+++++++++++++++++++++++++++++++++++++
unquote

In this example Toto & Titi should be in the same DIV. But in fact this is not
the case when using Firefox. In fact it looks like </noscript> is closing the
<DIV> that have been opened between <noscript> and </noscript>.
However If I remove the <noscript></noscript> tags, then I am getting the
relevant result.

But what is strange is that when JS is not enabled I should get the same result
whether there is <noscript></noscript> or not... and this is not the case

Thks & B.regards

Laurent

Comment 1

[Oliver Klee]

Over to Parser.

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

fwiw, that is invalid html, since the tags are wrongly nested

Comment 3

[Jens Bannmann]

(In reply to comment #2)
> fwiw, that is invalid html, since the tags are wrongly nested

Shouldn't this be resolved as INVALID or WONTFIX, then?

cohenlaur, you can't expect a browser to behave in a predictable way if you use
invalid HTML - the fact that it works in some could be interpreted as pure luck.
Make sure your HTML validates against validator.w3.org.

Comment 4

[Alexey Chernyak]

INVALID.