Closed
Bug 52136
Opened 26 years ago
Closed 26 years ago
NOSCRIPT content always displayed if it includes a BODY tag
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
Future
People
(Reporter: frank, Assigned: harishd)
References
()
Details
Attachments
(1 file)
|
372 bytes,
text/html
|
Details |
| Reporter | ||
Comment 1•26 years ago
|
||
The test case is wrong because the <body> tag
appears in an illegal place - you aren't
allowed a <body> _inside_ a <noscript> anyway.
It doesn't make any sense to use it for a start.
The noscript would go in the <noframes> tag or in
the separate frames in the case of a page like the
test case supplied.
| Reporter | ||
Comment 4•26 years ago
|
||
I don't dispute that it is illegal. Regardless, other browsers (Netscape 3.x -
4.x, IE 3.x - 5.x, Opera 4.x) handle it fine, and Mozilla used to display the
frameset (granted that is because it never displayed the NOSCRIPT content).
This is a change from past behavior, which is why I mention it.
It does cause real world damage though. Take a look at
http://www.sane.com/demo/NetTracker/web/index.html, this is a web browser based
product that is now totally useless because of this bug -- you can no longer get
to the frameset in Mozilla. We used the BODY tag inside the NOSCRIPT tag to set
the background color of the page people should get when they try to use our
product without JavaScript enabled.
However, due to a variety of other bugs in Mozilla, the released version of our
product looks like total **** anyway - so in a way I'm not totally unhappy that
people won't be able to use it at all. ;) We've patched the next release, which
works very well with Mozilla / NS6. I mention this bug for completeness - if
harishd wants to mark it INVALID I won't argue.
I wouldn't say INVALID because if every other version of Nav. and IE supports
this behavior then Mozilla should support too for backwards compatibility.
However, this bug is not so improtant to be tackled at this stage of the
project. So, I'm inclined to FUTURE this bug.
Marking FUTURE.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Harish: Please diagnose the problem. I'm inclined to fight a little harder on
this because it's a (relatively) common case.
This should be fixed now.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•