Closed Bug 46157 Opened 24 years ago Closed 24 years ago

Appears that JavaScript is not being rendered on M16

Categories

(Core :: DOM: HTML Parser, defect, P3)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
All
Type:
defect

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla0.9.1

People

(Reporter: jstanley, Assigned: harishd)

References

(
URL
)

Details

It would appear that JavaScript on this page is not being rendered correctly.
Using M16 on Win98 (not Win98SE).  I see the actual JavaScript code instead of
whatever it is supposed to produce.  This does not occur on Netscape 4.73.
*** Bug 46158 has been marked as a duplicate of this bug. ***
The offending line is the <script type="text/javascript" line which doesn't have
a >.  When I do a view source on mozilla, it adds the > on the next line
followed by a </script>.

That's not the whole story though.  Mozilla recovers from that statement, but
the comments that follow (Which should have been in the CDATA section of the
script element) can displayed on the screen, <!-- and everything.  This part is
certainly a bug.

I suspect this shouldn't be assigned to javascript, although I'm not quite sure
where it should go for coping with well-formedness problems.

Seen on Linux 200007181, changing OS to all and confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
I went to the given URL in both NN4.72 and Mozilla, and did View/Page Source.
Here are the first few lines in each case. I don't know why there are so many 
discrepancies. 

IN NN4.72:

<BASE HREF="http://www.postnet.com/postnet/stories.nsf/ByDocID/">
<HTML>
<!-- Lotus-Domino (Release 5.0.3 - March 21, 2000 on Windows NT/Intel) -->
<HEAD>
<SCRIPT TYPE="text/javascript"
<!-- postnet.com Javascript -->

<!-- 
function goThere(dbobj) {

             ETC.



IN MOZILLA: 

<HTML>
<!-- Lotus-Domino (Release 5.0.3 - March 21, 2000 on Windows NT/Intel)   -->
<HEAD>
<SCRIPT  TYPE-"text/javascript"
></script><!-- postnet.com Javascript -->
<!--
function goThere(dbobj) {

             ETC.


This looks to me like a matter for HTML parsing, and not the JS Engine itself. 
Reassigning to Parser component for acceptance or further triage. Please send 
back if you feel this is a JS Engine issue...
Assignee: rogerl → rickg
Component: Javascript Engine → Parser
QA Contact: pschwartau → janc
Invalid HTML. This problem can be easily fixed in the document.  Very low 
priority bug..moving to the FUTURE list.
Target Milestone: --- → Future
Off to harish to triage.
Assignee: rickg → harishd
Status: NEW → ASSIGNED
Target Milestone: Future → mozilla0.9.1
I think I landed a fix for this recently. Marking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
updated qa contact.
QA Contact: janc → bsharma
Verified on
build: 2001-05-29-20-Trunk
platform: Win NT

The page is displayed properly.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.