Problème de validation W3C (script pris pour du HTML)

Problème de validation W3C (script pris pour du HTML) - HTML/CSS - Programmation

Marsh Posté le 16-12-2009 à 15:22:47    

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 :
  1. <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. 1.   Warning  Line 145, Column 121: cannot generate system identifier for general entity "noui"
  3.       …open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(
  5.       ✉
  7.       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".
  9.       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 "&amp;" (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 &aelig; are different characters.
  11.       If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
  13.       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.    2. Error Line 145, Column 121: general entity "noui" not defined and no default entity
  16.       …open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(
  18.       ✉
  20.       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.
  21.    3. Error Line 145, Column 125: reference to entity "noui" for which no system identifier could be generated
  23.       …('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(loca
  25.       ✉
  27.       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.
  28.    4. Info Line 145, Column 119: entity was defined here
  30.       …w.open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponen
  32.    5. Warning Line 145, Column 126: cannot generate system identifier for general entity "jump"
  34.       …'http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(locat
  36.       ✉
  38.       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".
  40.       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 "&amp;" (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 &aelig; are different characters.
  42.       If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
  44.       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.
  45.    6. Error Line 145, Column 126: general entity "jump" not defined and no default entity
  47.       …'http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(locat
  49.       ✉
  51.       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.
  52.    7. Error Line 145, Column 130: reference to entity "jump" for which no system identifier could be generated
  54.       …p://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.
  56.       ✉
  58.       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.
  59.    8. Info Line 145, Column 124: entity was defined here
  61.       …n('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(loc
  63.    9. Warning Line 145, Column 137: cannot generate system identifier for general entity "url"
  65.       …icious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'
  67.       ✉
  69.       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".
  71.       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 "&amp;" (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 &aelig; are different characters.
  73.       If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
  75.       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.
  76.   10. Error Line 145, Column 137: general entity "url" not defined and no default entity
  78.       …icious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'
  80.       ✉
  82.       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.
  83.   11. Error Line 145, Column 140: reference to entity "url" for which no system identifier could be generated
  85.       …ous.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'&ti
  87.       ✉
  89.       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.
  90.   12. Info Line 145, Column 135: entity was defined here
  92.       …elicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)
  94.   13. Warning Line 145, Column 179: cannot generate system identifier for general entity "title"
  96.       …encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title
  98.       ✉
  100.       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".
  102.       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 "&amp;" (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 &aelig; are different characters.
  104.       If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.
  106.       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.
  107.   14. Error Line 145, Column 179: general entity "title" not defined and no default entity
  109.       …encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title
  111.       ✉
  113.       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.
  114.   15. Error Line 145, Column 184: reference to entity "title" for which no system identifier could be generated
  116.       …eURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'd
  118.       ✉
  120.       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.
  121.   16. Info Line 145, Column 177: entity was defined here
  123.       …'+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.tit


Message édité par caribouuu le 16-12-2009 à 15:28:14

---------------
Bla (blaa bbla)
Reply

Marsh Posté le 16-12-2009 à 15:22:47   

Reply

Marsh Posté le 16-12-2009 à 15:52:23    

Dans l'url que tu veux lancer, les paramètres sont séparés par des '&' or en xHTML, c'est un caractère réservé (début d'une entity).
 
C'est pourquoi il faut que tu mette &amp; à la place

Code :
  1. 'http://delicious.com/save?v=5&amp;noui&amp;jump=close&amp;url='+encodeURIComponent(location.href)+'&amp;title='+encodeURIComponent(document.title)

Reply

Marsh Posté le 16-12-2009 à 15:57:24    

je crois qu'il veut que tu remplace tes & par des &amp; dans ton url:

Code :
  1. <li id="delicious" ><a href="http://delicious.com/save" onclick="window.open('http://delicious.com/save?v=5&amp;noui&amp;jump=close&amp;url='+encodeURIComponent(location.href)+'&amp;title='+encodeURIComponent(document.title), 'delicious','toolbar=no,width=550,height=550'); return false;" title="">retrouvez mon site sur delicious</a></li>


 
 
 [:benou_grilled]  barbecued: ok, je vais me coucher.


Message édité par pataluc le 16-12-2009 à 15:58:28
Reply

Marsh Posté le 16-12-2009 à 16:06:36    

Merci les gars ! Je vais tester ça  :jap:


---------------
Bla (blaa bbla)
Reply

Marsh Posté le 16-12-2009 à 16:34:15    

Ca y est, c'est la consécration, je suis validé htmlemement conforme par le W3C :o
 
Merci encore ;)


---------------
Bla (blaa bbla)
Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed