"ASM" <stephanemoriaux.NoAdmin@wanadoo.fr.invalidwrote in message
news:45b6988f$0$5103$ba4acef3@news.orange.fr...
Quote:
Nospam a écrit :
Quote:
"ASM" <stephanemoriaux.NoAdmin@wanadoo.fr.invalidwrote in message
news:45b29811$0$25944$ba4acef3@news.orange.fr...
>
>
I can't do more : I haven'IE and that works in my FF and my Safari.
Must say I appreciate your help a greta deal :)
I put the code for sample3.html in the html validator at
http://validator.w3.org and it said it found 11 errors, I am thinking maybe
that is why i didn't work in IE, but have no idea how to go about the
changes, I tried it for sample4.html at
http://watchanimation.awardspace.com/sample4.html but I think made it worse
as the popup doesn't show. The errors for sample3.html from the validator
are:
Error Line 1 column 0: no document type declaration; implying "<!DOCTYPE
HTML SYSTEM>".
<html>
The checked page did not contain a document type ("DOCTYPE") declaration.
The Validator has tried to validate with a fallback DTD, but this is quite
likely to be incorrect and will generate a large number of incorrect error
messages. It is highly recommended that you insert the proper DOCTYPE
declaration in your document -- instructions for doing this are given
above -- and it is necessary to have this declaration before the page can be
declared to be valid.
?
Error Line 2 column 5: document type does not allow element "BODY" here.
<body>
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).
?
Error Line 20 column 3: document type does not allow element "LI" here;
missing one of "UL", "OL", "DIR", "MENU" start-tag.
<li>
The mentioned element is not allowed to appear in the context in which
you've placed it; the other mentioned elements are the only ones that are
both allowed there and can contain the element mentioned. This might mean
that you need a containing element, or possibly that you've forgotten to
close a previous element.
One possible cause for this message is that you have attempted to put a
block-level element (such as "<p>" or "<table>") inside an inline element
(such as "<a>", "<span>", or "<font>").
?
Warning Line 23 column 121: cannot generate system identifier for general
entity "url".
....m/flash/flvplayer.swf?20061026012254&url=http%3A%2F%2Fchi-v91.chi.youtube
..com
An entity reference was found in the document, but there is no reference by
that name defined. Often this is caused by misspelling the reference name,
unencoded ampersands, or by leaving off the trailing semicolon (;). The most
common cause of this error is unencoded ampersands in URLs as described by
the WDG in "Ampersands in URLs".
Entity references start with an ampersand (&) and end with a semicolon (;).
If you want to use a literal ampersand in your document you must encode it
as "&" (even inside URLs!). Be careful to end entity references with a
semicolon or your entity reference may get interpreted in connection with
the following text. Also keep in mind that named entity references are
case-sensitive; &Aelig; and æ are different characters.
If this error appears in some markup generated by PHP's session handling
code, this article has explanations and solutions to your problem.
Note that in most documents, errors related to entity references will
trigger up to 5 separate messages from the Validator. Usually these will all
disappear when the original problem is fixed.
?
Error Line 23 column 121: general entity "url" not defined and no default
entity.
....m/flash/flvplayer.swf?20061026012254&url=http%3A%2F%2Fchi-v91.chi.youtube
..com
This is usually a cascading error caused by a an undefined entity reference
or use of an unencoded ampersand (&) in an URL or body text. See the
previous message for further details.
?
Error Line 23 column 124: reference to entity "url" for which no system
identifier could be generated.
....lash/flvplayer.swf?20061026012254&url=http%3A%2F%2Fchi-v91.chi.youtube.co
m%2F
This is usually a cascading error caused by a an undefined entity reference
or use of an unencoded ampersand (&) in an URL or body text. See the
previous message for further details.
?
Info Line 23 column 120: entity was defined here.
....om/flash/flvplayer.swf?20061026012254&url=http%3A%2F%2Fchi-v91.chi.youtub
e.co
Error Line 25 column 5: document type does not allow element "LI" here;
missing one of "UL", "OL", "DIR", "MENU" start-tag.
<li>
?
Error Line 26 column 124: reference to entity "url" for which no system
identifier could be generated.
....lash/flvplayer.swf?20061026012254&url=http%3A%2F%2Fchi-v119.chi.youtube.c
om%2
?
Info Line 23 column 120: entity was defined here.
....om/flash/flvplayer.swf?20061026012254&url=http%3A%2F%2Fchi-v91.chi.youtub
e.co
Error Line 31 column 6: end tag for "HTML" which is not finished.
</html>
Most likely, You nested tags and closed them in the wrong order. For example
<p><em>...</pis not acceptable, as <emmust be closed before <p>.
Acceptable nesting is: <p><em>...</em></p>
Another possibility is that you used an element which requires a child
element that you did not include. Hence the parent element is "not
finished", not complete. For instance, <headgenerally requires a <title>,
lists (ul, ol, dl) require list items (li, or dt, dd), and so on.