<noscript> validation with XHTML problem

[Burton Figg]

My homepage, www.jimpix.co.uk uses transitional XHTML.

The whole thing validates except one line:

<noscript><im g height="1" width="1" alt=""
src="http://u0.extreme-dm.com/0.gif?tag=riggo tt&amp;j=n" /></noscript>

I get this error on this page:

http://validator.w3.org/check?uri=ht...w.jimpix.co.uk

Line 106, column 18: document type does not allow element "noscript" here;
missing one of "object", "applet", "map", "iframe", "button", "ins", "del"
start-tag

this is pointing to the start of the <noscript> tag.

I need the code to enable a site tracker I use (XTreme Tracking).

I have had a look on usenet and the web, but can't find anything to help
solve it.

Thanks

Jim

[Martin Honnen]

Burton Figg wrote:

My homepage, www.jimpix.co.uk uses transitional XHTML.

The whole thing validates except one line:

<noscript><im g height="1" width="1" alt=""
src="http://u0.extreme-dm.com/0.gif?tag=riggo tt&amp;j=n" /></noscript>

I get this error on this page:

http://validator.w3.org/check?uri=ht...w.jimpix.co.uk

Line 106, column 18: document type does not allow element "noscript" here;
missing one of "object", "applet", "map", "iframe", "button", "ins", "del"
start-tag

this is pointing to the start of the <noscript> tag.

As far as I can see the <noscript> is a child of a <p> element, if you
look at the definition for <p> you will find
<!ELEMENT p %Inline;>
with
<!ENTITY % Inline "(#PCDATA | %inline; | %misc.inline;)* ">
and with
<!ENTITY % misc.inline "ins | del | script">
and with
<!ENTITY % inline "a | %special; | %fontstyle; | %phrase; |
%inline.forms;" >
and none of those contain the <noscript> element which only occurs in

<!-- these can only occur at block level -->
<!ENTITY % misc "noscript | %misc.inline;">

so basically <noscript> is not allowed inside of a <p> element.

Of course your content is text/html and existing browsers for that
content type use tag soup parsers and don't care about placement of the
<noscript> element.

--

Martin Honnen
http://JavaScript.FAQTs.com/

[Brian]

Burton Figg wrote:

My homepage, www.jimpix.co.uk uses transitional XHTML.
Out of curiousity, why xhtml and not html? and why transitional and
not strict?
The whole thing validates except one line:

<noscript><im g height="1" width="1" alt=""
src="http://u0.extreme-dm.com/0.gif?tag=riggo tt&amp;j=n" /></noscript>

I get this error on this page:

Line 106, column 18: document type does not allow element "noscript" here;
missing one of "object", "applet", "map", "iframe", "button", "ins", "del"
start-tag
The noscript element's child must be a block level element. <img> is
inline.
I need the code to enable a site tracker I use (XTreme Tracking).
That sounds unfortunate.
I have had a look on usenet and the web, but can't find anything to help
solve it.

<noscript>
<div>
<img height="1" width="1" alt=""
src="http://u0.extreme-dm.com/0.gif?tag=riggo tt&amp;j=n" />
</div>
</noscript>

--
Brian
follow the directions in my address to email me

[Martin Honnen]

Brian wrote:

Burton Figg wrote:

My homepage, www.jimpix.co.uk uses transitional XHTML. I get this error on this page:

Line 106, column 18: document type does not allow element "noscript"
here;
missing one of "object", "applet", "map", "iframe", "button", "ins",
"del"
start-tag

The noscript element's child must be a block level element. <img> is
inline.

With the transitional document type the noscript content is flow which
allows inline or block content.

--

Martin Honnen
http://JavaScript.FAQTs.com/

[Brian]

Martin Honnen wrote:

Brian wrote:

Burton Figg wrote:

My homepage, www.jimpix.co.uk uses transitional XHTML. I get this error on this page:

Line 106, column 18: document type does not allow element
"noscript" here; missing one of "object", "applet", "map",
"iframe", "button", "ins", "del" start-tag

The noscript element's child must be a block level element.
<img> is inline.

With the transitional document type the noscript content is flow
which allows inline or block content.

Oops. My bad. I've never used html transitional, and am unfamiliar
with its dtd. I failed to consider that noscript might be different
in regards to allowed content. My apologies.

--
Brian
follow the directions in my address to email me

[Brian]

Martin Honnen wrote:

Brian wrote:

The noscript element's child must be a block level element.
<img> is inline.

With the transitional document type the noscript content is flow
which allows inline or block content.

I must say, upon reflection, I'm puzzled by this. Why is inline
content allowed in the transitional dtd, but not in the strict one? I
don't see this as a presentational (x)html issue.

--
Brian
follow the directions in my address to email me

[David Dorward]

Brian wrote:

With the transitional document type the noscript content is flow
which allows inline or block content.

I must say, upon reflection, I'm puzzled by this. Why is inline
content allowed in the transitional dtd, but not in the strict one? I
don't see this as a presentational (x)html issue.

Becuase the difference between Transitional and Strict is not just about the
removal of presentational markup.

--
David Dorward <http://dorward.me.uk/>

[Nick Kew]

In article <bs**********@t itan.btinternet .com>, one of infinite monkeys
at the keyboard of "Burton Figg" <so*****@somewh ere.com> wrote:

Line 106, column 18: document type does not allow element "noscript" here;
missing one of "object", "applet", "map", "iframe", "button", "ins", "del"
start-tag

Can't check while I'm offline, but that probably means you've put
<noscript> in an inline element. I expect you'd also get a more
helpful error message from Page Valet or the WDG Validator.

--
Nick Kew

In urgent need of paying work - see http://www.webthing.com/~nick/cv.html

[Andy Dingley]

On Tue, 30 Dec 2003 13:49:28 +0000 (UTC), "Burton Figg"
<so*****@somewh ere.com> wrote:

The whole thing validates except one line: [...]this is pointing to the start of the <noscript> tag.

Martin has pointed out your specific problem - but as a general rule,
validators never point out where the error _is_, they point out the
place where the error becomes obvious. The thing causing it is almost
always earlier on in the input.

--
Klein bottle for rent. Apply within.

[Anne van Kesteren]

Nick Kew wrote:

Can't check while I'm offline, but that probably means you've put
<noscript> in an inline element. I expect you'd also get a more
helpful error message from Page Valet or the WDG Validator.

Correct. <noscript/> may not appear within <font/> or any other inline
element.

<font/> shouldn't appear at all on a page, but that is a different subject.

--
Anne van Kesteren
<http://www.annevankest eren.nl/>