W3C home > Mailing lists > Public > www-validator@w3.org > May 2010

Re: [VE][64] Add Subject Here

From: Michael(tm) Smith <mike@w3.org>
Date: Wed, 26 May 2010 14:43:20 +0900
To: dave <davebrown6502361@hotmail.com>
Cc: www-validator@w3.org
Message-ID: <20100526054319.GI21306@sideshowbarker>
dave <davebrown6502361@hotmail.com>, 2010-05-25 11:32 -0700:

> Validating
> Error [64]: "document type does not allow element X here"

The root cause of that seems to be that document has some "<"
characters in the content of the script element that starts on
line 15; e.g., this part:

  COMVERSE.utils.FUNNYCHARS = "&\'*:<>\"\\?|~/#{}";

and this:

  installPlayer: '<a class="install_player" target="_blank"

And you have an XHTML doctype on the document, so the W3C Markup
Validator is trying to parse it as an actual XML/XHTML document,
and in XML/XHTML documents, unescaped "<" chars are not allowed.

The thing is, though, that document is actually being served as
text/html (not as XML/XHTML), so browsers process it fine, in
spite of the "error" about the "<" character.

That document actually comes close to validating as HTML5; see:
or http://a.gd/6edd21

So if you fix those errors, you can be confident that it will be
processed as expected by browsers. The fixes you'd need to make are:

1. Change the doctype to either an HTML or XHTML *Strict* doctype
instead of Transitional. (Serving a document with a Transitional
doctype causes browsers to parse it in "quirks mode", which is
almost certainly not what you want happening.)

2. Completely delete the <meta http-equiv="expires" content="-1" />
instance; it has no effect in browsers at all.

3. Change the fragment ID reference in "#Password tip" (line 97)
with "#Password%20tip" or with a fragment ID that does not have a
space it in at all.

Michael(tm) Smith
Received on Wednesday, 26 May 2010 05:43:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:59:17 UTC