Closed Bug 203398 Opened 21 years ago Closed 21 years ago

<script ... /> breaks inline javascript (in text/html)

Categories

(Core :: DOM: HTML Parser, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 162653

People

(Reporter: theseer, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401

I have an XHTML 1.0 transitional conforming page loading an external javascript
by using a selfcontained <script ..... />.
A function defined inline (and wrapped in CDATA which seems to have no effect
whatsoever on mozilla ) right afterwards is ignored ( see URL )




Reproducible: Always

Steps to Reproduce:
1. Load URL



Actual Results:  
Error 'say is not defined' in Javascript Console

Expected Results:  
Popup stateing 'This is a test'

Change the URL to http://dev.stage.tow.de/mozilla/working.html to see the
'working' version ( <script ... />  became <script ...></script> )

This bug - though i consider it 'normal' priority - is pretty annoying to me,
since  the html is generated using XSL and/or DOM where empty tags are
'optimized'  so i can hardly work around this problem.
You're serving the page as "text/html" but using XML syntax, which we don't
support and should not support. Use the correct MIME-type
("application/xml+xhtml" or "application/xml") or stop generating this kind of
XHTML. (See XHTML 1.0 Appendix C for some guidelines on
"backwards-compatibility"). INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
*** Bug 212757 has been marked as a duplicate of this bug. ***
*** Bug 233093 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
*** Bug 324996 has been marked as a duplicate of this bug. ***
*** Bug 329384 has been marked as a duplicate of this bug. ***
Summary: <script ... /> breaks inline javascript → <script ... /> breaks inline javascript (in text/html)
*** Bug 349291 has been marked as a duplicate of this bug. ***
*** Bug 362765 has been marked as a duplicate of this bug. ***
Resolution: INVALID → DUPLICATE
Whether <script ... /> is invalid or not, it's pretty hard for me to believe that the desired behavior is to render a blank screen with no error messages in the js console.  This drove me crazy for about 30 minutes trying to debug!

This bug should not be marked resolved until it at least displays an error message *somewhere* in the browser.
An error message on the console would certainly be nice.  Please file a new bug report for that.
Assignee: asa → nobody
Component: General → HTML: Parser
OS: Linux → All
Product: SeaMonkey → Core
QA Contact: asa → parser
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.