caribouuu | Bonjour
Je suis en train de faire mon site internet, et j'ai un petit problème de validation WC3, en fait le validator me trouve 8 erreurs sur une seule ligne de code.
C'est une ligne de code javascript, (lien "delicious" )
Code :
- <li id="delicious" ><a href="http://delicious.com/save" onclick="window.open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'delicious','toolbar=no,width=550,height=550'); return false;" title="">retrouvez mon site sur delicious</a></li>
|
Les erreurs sont exclusivement dans la partie javascript. Est-ce que quelqu'un saurait s'il y a quelque chose à faire pour que le validator comprenne que c'est pas du HTML mais un script?
Je vous montre les erreurs signalées par le validator, mais je suis pas sûr que ce soit utile, juste au cas ou....(j'ai le pressentiment que toutes les erreurs ont la même cause et pourraient être résolues par une manip que j'ignore. )
Code :
- 1. Warning Line 145, Column 121: cannot generate system identifier for general entity "noui"
- …open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(
- ✉
- 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.
- 2. Error Line 145, Column 121: general entity "noui" not defined and no default entity
- …open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(
- ✉
- 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.
- 3. Error Line 145, Column 125: reference to entity "noui" for which no system identifier could be generated
- …('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(loca
- ✉
- 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.
- 4. Info Line 145, Column 119: entity was defined here
- …w.open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponen
- 5. Warning Line 145, Column 126: cannot generate system identifier for general entity "jump"
- …'http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(locat
- ✉
- 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.
- 6. Error Line 145, Column 126: general entity "jump" not defined and no default entity
- …'http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(locat
- ✉
- 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.
- 7. Error Line 145, Column 130: reference to entity "jump" for which no system identifier could be generated
- …p://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.
- ✉
- 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.
- 8. Info Line 145, Column 124: entity was defined here
- …n('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(loc
- 9. Warning Line 145, Column 137: cannot generate system identifier for general entity "url"
- …icious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'
- ✉
- 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.
- 10. Error Line 145, Column 137: general entity "url" not defined and no default entity
- …icious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'
- ✉
- 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.
- 11. Error Line 145, Column 140: reference to entity "url" for which no system identifier could be generated
- …ous.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'&ti
- ✉
- 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.
- 12. Info Line 145, Column 135: entity was defined here
- …elicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)
- 13. Warning Line 145, Column 179: cannot generate system identifier for general entity "title"
- …encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title
- ✉
- 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.
- 14. Error Line 145, Column 179: general entity "title" not defined and no default entity
- …encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title
- ✉
- 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.
- 15. Error Line 145, Column 184: reference to entity "title" for which no system identifier could be generated
- …eURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'd
- ✉
- 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.
- 16. Info Line 145, Column 177: entity was defined here
- …'+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.tit
|
Message édité par caribouuu le 16-12-2009 à 15:28:14
---------------
Bla (blaa bbla)
|
![[:benou_grilled]](https://forum-images.hardware.fr/images/perso/benou_grilled.gif "[:benou_grilled]")
barbecued: ok, je vais me coucher.
