SGML Parser doesn't like <script> contents?

(Pete Cresswell) · Dec 24, 2004

This code:
--------------
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<base target="40thPix_DisplayArea"/>
<title> Click on a small picture...</title>
<link rel="stylesheet" type="text/css" href="Master.css"/>
<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
</head>

<body>
<script type="text/javascript">
document.write("<p id='ThumbNavListloading'>Loading thumbnails, please
wait...<\/p>");
........
</script>
--------------

makes the W3C's SGML parser flag the 'document.write' line with
-------------------------------------
Line 12, column 45: document type does not allow element "p" here

....nt.write("<p id='ThumbNavListloading'>Loading thumbnails, please wait...<\/p>

The element named above was found in a context where it is not allowed. This
could mean that you have incorrectly nested elements -- such as a "style"
element in the "body" section instead of inside "head" -- or two elements that
overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents.
Due to HTML's rules of implicitly closed elements, this error can create
cascading effects. For instance, using XHTML's "self-closing" tags for "meta"
and "link" in the "head" section of a HTML document may cause the parser to
infer the end of the "head" section and the beginning of the "body" section
(where "link" and "meta" are not allowed; hence the reported error).
-------------------------------------

Seems like it's not buying the <script> command - but the code works, so
*somebody* is recognizing it.

Can anybody tell me where I've sinned?

Oli Filth · Dec 24, 2004

From what I remember, it's good practice to always surround your
Javascript with comment delimiters, e.g.

<SCRIPT type="text/javascript">

</SCRIPT>

That way, anything that doesn't know Javascript won't see it, because
it's commented out.

Oli

rf · Dec 24, 2004

wrote:Oli Filth wrote:

(Pete Cresswell) said:
From what I remember, it's good practice to always surround your
Javascript with comment delimiters, e.g.

<SCRIPT type="text/javascript">

</SCRIPT>

That way, anything that doesn't know Javascript won't see it, because
it's commented out.

Nope. That is cargo cult stuff that went out of fashion with release 3
browsers.

In XHTML anything inside a script element is cdata and should be marked as
such:

<SCRIPT type="text/javascript">
<![cdata[
.... script goes here ...
]]>
</SCRIPT>

google for "xhtml cdata".

The (better) alternative is put the javascript in an external file and link
to it.

Pete, if you are going to all the hassle of using XHTML (including the fact
that IE does not understand it) why are you using transitional rather than
strict?

(Pete Cresswell) · Dec 24, 2004

RE/

it's good practice to always surround your
Javascript with comment delimiters, e.g.

Bingo! And everybody's happy...

Thanks.

Neal · Dec 24, 2004

RE/

Bingo! And everybody's happy...

I'm not happy... see rf's response for a more appropriate solution.

Oli Filth · Dec 24, 2004

Oh, sorry, didn't spot the XHTML doctype. I stand corrected.

Oli

wrote:Oli Filth wrote:
(Pete Cresswell) wrote:

From what I remember, it's good practice to always surround your
Javascript with comment delimiters, e.g.

<SCRIPT type="text/javascript">

</SCRIPT>

That way, anything that doesn't know Javascript won't see it, because
it's commented out.

Click to expand...

Nope. That is cargo cult stuff that went out of fashion with release 3
browsers.

In XHTML anything inside a script element is cdata and should be marked as
such:

<SCRIPT type="text/javascript">
<![cdata[
... script goes here ...
]]>
</SCRIPT>

google for "xhtml cdata".

The (better) alternative is put the javascript in an external file and link
to it.

Pete, if you are going to all the hassle of using XHTML (including the fact
that IE does not understand it) why are you using transitional rather than
strict?

Duende · Dec 24, 2004

While sitting in a puddle rf scribbled in the mud:

The (better) alternative is put the javascript in an external file and link
to it.

The best place to put it is... Recycle Bin

Phoenix · Dec 24, 2004

(Pete Cresswell) wrote:

<body>
<script type="text/javascript">
document.write("<p id='ThumbNavListloading'>Loading thumbnails, please
wait...<\/p>");
.......
</script>

Seems like it's not buying the <script> command - but the code works, so
*somebody* is recognizing it.

Can anybody tell me where I've sinned?

Notice also, that if you are ever going to send this as TRUE XHTML (that
is with the document type of "application/xhtml+xml" and not as HTML
(text/html), document.write() will stop working.

David Håsäther · Dec 24, 2004

No, it's not commented out (supposing this is CDATA declared content),
although in a UA that doesn't support the SCRIPT element type it will
likely be, yes. But as rf said, this is things that belongs to the
past.

In XHTML anything inside a script element is cdata

No, the content model for script is (#PCDATA) in XHTML.

Dylan Parry · Dec 24, 2004

Neal said:
I'm not happy... <snip/>

Can't please everyone

The OP wants to use Javascript, Oli wants to use comments to hide it,
Richard wants to use CDATA, David wants PCDATA, and Duende wants the OP
to not use Javascript at all :s

Me? I'm indifferent

(Pete Cresswell) · Dec 24, 2004

RE/

Pete, if you are going to all the hassle of using XHTML (including the fact
that IE does not understand it) why are you using transitional rather than
strict?

Because I'm still suffering from RCI HTML-wise.

I probably copied that line from somewhere and it worked...so I never touched
it.

I've gotten all my code through W3C's parser with no fatals - as "Transitional".
Sounds like it's time to find an upgraded !DOCTYPE statement and try strict

(Pete Cresswell) · Dec 24, 2004

RE/

Notice also, that if you are ever going to send this as TRUE XHTML (that
is with the document type of "application/xhtml+xml" and not as HTML
(text/html), document.write() will stop working.

That's definately in the works.

Which remedy should I adopt?

<![cdata[......]]> ?

(Pete Cresswell) · Dec 24, 2004

RE/

Notice also, that if you are ever going to send this as TRUE XHTML (that
is with the document type of "application/xhtml+xml" and not as HTML
(text/html), document.write() will stop working.

Can somebody point me to a page that asks for full enforcement of true XHTML?

I've looked through a half-dozen and found mostly HTML.

Spartanicus · Dec 24, 2004

(Pete Cresswell) said:
That's definately in the works.

Don't: http://www.spartanicus.utvinternet.ie/no-xhtml.htm

Dylan Parry · Dec 24, 2004

Spartanicus wrote:
[XHTML]

Don't: http://www.spartanicus.utvinternet.ie/no-xhtml.htm

The problem here is that your reasons why to _not_ use XHTML are about
as compelling as the reasons to use it, so the deciding factor is
whether the coder wants to use it or not. :\

(Pete Cresswell) · Dec 24, 2004

RE/

Don't: http://www.spartanicus.utvinternet.ie/no-xhtml.htm

Are XHTML and CSS inextricably intertwined or can I base formatting on a common
CSS file and still use plain-vanilla HTML?

Mitja · Dec 24, 2004

Are XHTML and CSS inextricably intertwined or can I base formatting on a
common CSS file and still use plain-vanilla HTML?

Sure you can.

Neal · Dec 24, 2004

RE/

Are XHTML and CSS inextricably intertwined or can I base formatting on a
common
CSS file and still use plain-vanilla HTML?

The elements in XHTML 1.0 and HTML 4.01 are identical, so the stylesheet
should not have to change.

Dylan Parry · Dec 24, 2004

(Pete Cresswell) said:
Are XHTML and CSS inextricably intertwined or can I base formatting on a common
CSS file and still use plain-vanilla HTML?

XHTML *is* HTML just with an X. There's no reason for you not to use CSS
with either. So, no they are not intertwined, and you can use CSS with
HTML as well as with XHTML

Neal · Dec 24, 2004

Dylan said:
XHTML *is* HTML just with an X.

So we must use XCSS, right? And XJavascript, XFlash, and lay it all out
with Xtables in an Xframeset!

An unknown bug doesn't allow the quotes app to work. What's the issue?	3	Apr 23, 2023
Issue with textbox script?	0	Sep 5, 2022
Script stops working when using variables to save time typing...	4	Oct 31, 2022
Why doesn't the function get called?	1	Nov 20, 2023
Help with Visual Lightbox: Scripts	2	May 3, 2023
JQuery add shadow error	4	Sep 1, 2023
XHTML - how extend/create ELEMENT body in my DTD?	0	Oct 29, 2019
I need help making an html website	2	Aug 2, 2023

SGML Parser doesn't like <script> contents?

(Pete Cresswell)

Oli Filth

rf

(Pete Cresswell)

Neal

Oli Filth

Duende

Phoenix

David Håsäther

Dylan Parry

(Pete Cresswell)

(Pete Cresswell)

(Pete Cresswell)

Spartanicus

Dylan Parry

(Pete Cresswell)

Mitja

Neal

Dylan Parry

Neal

Ask a Question

Similar Threads

Members online

Forum statistics

Latest Threads