Mon site n'est visible que sur Firefox !
MyBelovedMonster
Messages postés
3
Date d'inscription
Statut
Membre
Dernière intervention
-
RAD ZONE Messages postés 5230 Date d'inscription Statut Contributeur Dernière intervention -
RAD ZONE Messages postés 5230 Date d'inscription Statut Contributeur Dernière intervention -
Bonjour,
Je tiens un fansite dédié à l'actrice Kristen Stewart. Cela fait quelques temps que je manipule le HTML. En général, je n'ai aucun soucis avec mes pages. Cependant, les sites que je crée ont tendance à mal apparaître sous Internet Explorer (fond blanc!). Dernièrement, j'ai changé les pages du site pour modifier l'affichage, et voilà que les frames ne sont plus visibles sous Internet Explorer !
J'aimerais beaucoup que vous m'aidiez à les faire apparaître et si, en plus de cela, vous pouviez m'expliquer comment faire en sorte que mes frames apparaissent normalement sous IE.
Merci d'avance pour vos réponses.
Cordialement,
C.
Je tiens un fansite dédié à l'actrice Kristen Stewart. Cela fait quelques temps que je manipule le HTML. En général, je n'ai aucun soucis avec mes pages. Cependant, les sites que je crée ont tendance à mal apparaître sous Internet Explorer (fond blanc!). Dernièrement, j'ai changé les pages du site pour modifier l'affichage, et voilà que les frames ne sont plus visibles sous Internet Explorer !
J'aimerais beaucoup que vous m'aidiez à les faire apparaître et si, en plus de cela, vous pouviez m'expliquer comment faire en sorte que mes frames apparaissent normalement sous IE.
Merci d'avance pour vos réponses.
Cordialement,
C.
A voir également:
- Mon site n'est visible que sur Firefox !
- Site de telechargement - Accueil - Outils
- Site comme coco - Accueil - Réseaux sociaux
- Quel site remplace coco - Accueil - Réseaux sociaux
- Site x - Guide
- Site pour vendre des objets d'occasion - Guide
7 réponses
Je ne comprends pas grand chose à leur truc, là
ca ne m etonne pas !!
ca ne sert a rien de mettre une tartine qui ne t aide pas , c est sur !!
alors pour commencer tu vas mettre un doctype tout en haut de ta page , et on verra apres le reste !
ca ne m etonne pas !!
ca ne sert a rien de mettre une tartine qui ne t aide pas , c est sur !!
alors pour commencer tu vas mettre un doctype tout en haut de ta page , et on verra apres le reste !
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Commencer par faire évaluer la conformité du code aux normes en vigueur, c'est rapide et gratuit :
http://validator.w3.org/
Cordialement,
http://validator.w3.org/
Cordialement,
si tu donnais l'adresse de ton site je pense que l'on pourrait surement trouver d'ou vient le problème car comme ca sans aucune donnée cela va être très très très dur !
Oh quelle tête en l'air ! Je suis navrée mais merci de me le rappeler !
http://beautifulchild.online.fr
http://beautifulchild.online.fr
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Réponses du site de validation précité :
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
↑ Top
Validation Output: 15 Errors
Line 1, Column 1: 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.
Line 4, Column 24: non SGML character number 149
<title>BEAUTIFUL CHILD • a kristen stewart fansite | MOZILLA FIREFOX |</title>✉
You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.
Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.
This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.
Line 13, Column 18: character "ï" is not allowed in the value of attribute "NAME"
<meta name="descrïption" content="Votre ultime source francophone sur Kristen St✉
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
Line 26, Column 83: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
…lpadding="0" cellspacing="0" height="40">✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 28, Column 44: start tag for "TR" omitted, but its declaration does not permit this
…ight="40" align="center" width="100"><a class="navmenu" target="contenu" href✉
Line 36, Column 129: duplicate specification of attribute "TARGET"
…vejournal.com/beautiful_ks/" target="contenu">LiveJournal</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 38, Column 130: duplicate specification of attribute "TARGET"
…d.online.fr/FORUM/index.php" target="contenu">Communauté</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 40, Column 101: duplicate specification of attribute "TARGET"
…nu" href="ONLINE/index.html" target="contenu">Online</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 42, Column 122: duplicate specification of attribute "TARGET"
…erfect-bliss.net/webtop.htm" target="contenu">Votez !</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 47, Column 6: end tag for element "TD" which is not open
</td>✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 51, Column 18: Attribute "BORDER" is not a valid attribute. Did you mean "border"?
<iframe border="0" name="menu" src="colonne2.html" style="position: absolute; ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 182: Attribute "ALLOWTRANSPARENCY" is not a valid attribute
… overflow: auto;" allowtransparency="true" frameborder="0"></iframe>✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 52, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 55, Column 7: end tag for "TABLE" omitted, but its declaration does not permit this
</body>✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
Line 26: start tag was here
h<table width="800" border="0" align="left" cellpadding="0" cellspacing="0" heigh
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
↑ Top
Validation Output: 15 Errors
Line 1, Column 1: 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.
Line 4, Column 24: non SGML character number 149
<title>BEAUTIFUL CHILD • a kristen stewart fansite | MOZILLA FIREFOX |</title>✉
You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.
Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.
This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.
Line 13, Column 18: character "ï" is not allowed in the value of attribute "NAME"
<meta name="descrïption" content="Votre ultime source francophone sur Kristen St✉
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
Line 26, Column 83: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
…lpadding="0" cellspacing="0" height="40">✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 28, Column 44: start tag for "TR" omitted, but its declaration does not permit this
…ight="40" align="center" width="100"><a class="navmenu" target="contenu" href✉
Line 36, Column 129: duplicate specification of attribute "TARGET"
…vejournal.com/beautiful_ks/" target="contenu">LiveJournal</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 38, Column 130: duplicate specification of attribute "TARGET"
…d.online.fr/FORUM/index.php" target="contenu">Communauté</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 40, Column 101: duplicate specification of attribute "TARGET"
…nu" href="ONLINE/index.html" target="contenu">Online</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 42, Column 122: duplicate specification of attribute "TARGET"
…erfect-bliss.net/webtop.htm" target="contenu">Votez !</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 47, Column 6: end tag for element "TD" which is not open
</td>✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 51, Column 18: Attribute "BORDER" is not a valid attribute. Did you mean "border"?
<iframe border="0" name="menu" src="colonne2.html" style="position: absolute; ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 182: Attribute "ALLOWTRANSPARENCY" is not a valid attribute
… overflow: auto;" allowtransparency="true" frameborder="0"></iframe>✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 52, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 55, Column 7: end tag for "TABLE" omitted, but its declaration does not permit this
</body>✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
Line 26: start tag was here
h<table width="800" border="0" align="left" cellpadding="0" cellspacing="0" heigh
Réponses du site de validation précité :
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
↑ Top
Validation Output: 15 Errors
Line 1, Column 1: 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.
Line 4, Column 24: non SGML character number 149
<title>BEAUTIFUL CHILD • a kristen stewart fansite | MOZILLA FIREFOX |</title>✉
You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.
Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.
This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.
Line 13, Column 18: character "ï" is not allowed in the value of attribute "NAME"
<meta name="descrïption" content="Votre ultime source francophone sur Kristen St✉
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
Line 26, Column 83: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
…lpadding="0" cellspacing="0" height="40">✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 28, Column 44: start tag for "TR" omitted, but its declaration does not permit this
…ight="40" align="center" width="100"><a class="navmenu" target="contenu" href✉
Line 36, Column 129: duplicate specification of attribute "TARGET"
…vejournal.com/beautiful_ks/" target="contenu">LiveJournal</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 38, Column 130: duplicate specification of attribute "TARGET"
…d.online.fr/FORUM/index.php" target="contenu">Communauté</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 40, Column 101: duplicate specification of attribute "TARGET"
…nu" href="ONLINE/index.html" target="contenu">Online</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 42, Column 122: duplicate specification of attribute "TARGET"
…erfect-bliss.net/webtop.htm" target="contenu">Votez !</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 47, Column 6: end tag for element "TD" which is not open
</td>✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 51, Column 18: Attribute "BORDER" is not a valid attribute. Did you mean "border"?
<iframe border="0" name="menu" src="colonne2.html" style="position: absolute; ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 182: Attribute "ALLOWTRANSPARENCY" is not a valid attribute
… overflow: auto;" allowtransparency="true" frameborder="0"></iframe>✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 52, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 55, Column 7: end tag for "TABLE" omitted, but its declaration does not permit this
</body>✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
Line 26: start tag was here
h<table width="800" border="0" align="left" cellpadding="0" cellspacing="0" heigh
Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
Unable to Determine Parse Mode!
The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:
the MIME Media Type (text/html) can be used for XML or SGML document types
No known Document Type could be detected
No XML declaration (e.g <?xml version="1.0"?>) could be found at the beginning of the document.
No XML namespace (e.g <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">) could be found at the root of the document.
As a default, the validator is falling back to SGML mode.
No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.
No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.
The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.
Learn how to add a doctype to your document from our FAQ.
↑ Top
Validation Output: 15 Errors
Line 1, Column 1: 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.
Line 4, Column 24: non SGML character number 149
<title>BEAUTIFUL CHILD • a kristen stewart fansite | MOZILLA FIREFOX |</title>✉
You have used an illegal character in your text. HTML uses the standard UNICODE Consortium character repertoire, and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 inclusive) that are sometimes used for typographical quote marks and similar in proprietary character sets. The validator has found one of these undefined characters in your document. The character may appear on your browser as a curly quote, or a trademark symbol, or some other fancy glyph; on a different computer, however, it will likely appear as a completely different character, or nothing at all.
Your best bet is to replace the character with the nearest equivalent ASCII character, or to use an appropriate character entity. For more information on Character Encoding on the web, see Alan Flavell's excellent HTML Character Set Issues reference.
This error can also be triggered by formatting characters embedded in documents by some word processors. If you use a word processor to edit your HTML documents, be sure to use the "Save as ASCII" or similar command to save the document without formatting information.
Line 13, Column 18: character "ï" is not allowed in the value of attribute "NAME"
<meta name="descrïption" content="Votre ultime source francophone sur Kristen St✉
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
Line 26, Column 83: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
…lpadding="0" cellspacing="0" height="40">✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 28, Column 44: start tag for "TR" omitted, but its declaration does not permit this
…ight="40" align="center" width="100"><a class="navmenu" target="contenu" href✉
Line 36, Column 129: duplicate specification of attribute "TARGET"
…vejournal.com/beautiful_ks/" target="contenu">LiveJournal</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 38, Column 130: duplicate specification of attribute "TARGET"
…d.online.fr/FORUM/index.php" target="contenu">Communauté</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 40, Column 101: duplicate specification of attribute "TARGET"
…nu" href="ONLINE/index.html" target="contenu">Online</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 42, Column 122: duplicate specification of attribute "TARGET"
…erfect-bliss.net/webtop.htm" target="contenu">Votez !</a></td>✉
You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.
Line 47, Column 6: end tag for element "TD" which is not open
</td>✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
Line 51, Column 18: Attribute "BORDER" is not a valid attribute. Did you mean "border"?
<iframe border="0" name="menu" src="colonne2.html" style="position: absolute; ✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 182: Attribute "ALLOWTRANSPARENCY" is not a valid attribute
… overflow: auto;" allowtransparency="true" frameborder="0"></iframe>✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 51, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 52, Column 204: document type does not allow element "IFRAME" here; missing one of "TH", "TD" start-tag
…wtransparency="true" frameborder="0"></iframe>✉
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>").
Line 55, Column 7: end tag for "TABLE" omitted, but its declaration does not permit this
</body>✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.
Line 26: start tag was here
h<table width="800" border="0" align="left" cellpadding="0" cellspacing="0" heigh
