none
W3C XHTML1 Validation fails

    Question

  • Hi,

    I ran a check after using the EW clean up and HTML optimization.

    Why does Expression Web not conforming to standarts?


     

    Validation Output: 22 Errors

    1. Error Line 1, Column 357: required attribute "type" not specified.
      …&amp;title=&amp;border=&amp;output=js"></script>

      The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

      Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

    2. Error Line 1, Column 357: document type does not allow element "script" here; assuming missing "head" start-tag.
      …&amp;title=&amp;border=&amp;output=js"></script>

    3. Error Line 3, Column 5: document type does not allow element "head" here.
      <head><meta content="mobile112TM - mobile scanner - mobile c-pen - læsehjælp - m

      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).

    4. Error Line 7, Column 267: document type does not allow element "a" here; assuming missing "object" start-tag.
      …74o-c%61p%74ur%61.dk'" title="e-mail">e-mail </a><title>start</title><link hr

    5. Error Line 7, Column 285: document type does not allow element "title" here.
      …dk'" title="e-mail">e-mail </a><title>start</title><link href="styles/style2.

      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).

    6. Error Line 7, Column 364: document type does not allow element "link" here.
      …s" rel="stylesheet" type="text/css" /><style type="text/css">

      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).

    7. Error Line 7, Column 387: document type does not allow element "style" here.
      …e="text/css" /><style type="text/css">

      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).

    8. Error Line 51, Column 6: end tag for "object" omitted, but OMITTAG NO was specified.
      </head><body><div id="container"><div id="masthead" class="style1"><h1 class="st

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

    9. Info Line 7, Column 69: start tag was here.
      …t=utf-8" http-equiv="Content-Type" /><a href="sitemap.htm" originalAttribute="href" originalPath="sitemap.htm" onfocus="this.href
    10. Error Line 51, Column 6: end tag for "head" which is not finished.
      </head><body><div id="container"><div id="masthead" class="style1"><h1 class="st

      Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must 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, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.

    11. Error Line 51, Column 12: document type does not allow element "body" here.
      </head><body><div id="container"><div id="masthead" class="style1"><h1 class="st

      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).

    12. Error Line 51, Column 2381: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag.
      … mobile version 6.1 <p class="style8"><img alt="ny htc til motto" class="styl

      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>").

    13. Error Line 51, Column 2781: end tag for "span" omitted, but OMITTAG NO was specified.
      …c="menu.jpg" width="106" /> </p></div><div id="footer"><p><a href="index.html

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

    14. Info Line 51, Column 1592: start tag was here.
      …l dokumentlæseren">e-bog.</a></h2><p><span>Ny <a href="http://www.motto-captu
    15. Error Line 51, Column 2781: end tag for "p" omitted, but OMITTAG NO was specified.
      …c="menu.jpg" width="106" /> </p></div><div id="footer"><p><a href="index.html

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

    16. Info Line 51, Column 1589: start tag was here.
      … til dokumentlæseren">e-bog.</a></h2><p><span>Ny <a href="http://www.motto-ca
    17. Error Line 51, Column 3599: "head" not finished but containing element ended.
      …an> </a></p></div></div></body></html>

    18. Error Line 51, Column 3599: end tag for "head" omitted, but OMITTAG NO was specified.
      …an> </a></p></div></div></body></html>

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

    19. Info Line 1, Column 174: start tag was here.
      … xmlns="http://www.w3.org/1999/xhtml"><script src="http://www.gmodules.com/ig
    20. Error Line 51, Column 3599: end tag for "html" which is not finished.
      …an> </a></p></div></div></body></html>

      Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must 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, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.

    21. Error Line 51, Column > 80: XML Parsing Error: Opening and ending tag mismatch: span line 51 and div.
      …asthead" class="style1"><h1 class="style4">motto-captura</h1><h3 class="style…

    22. Error Line 51, Column > 80: XML Parsing Error: Opening and ending tag mismatch: p line 51 and div.
      …asthead" class="style1"><h1 class="style4">motto-captura</h1><h3 class="style…

    23. Error Line 51, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 51 and body.
      …asthead" class="style1"><h1 class="style4">motto-captura</h1><h3 class="style…

    24. Error Line 51, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 51 and html.
      …asthead" class="style1"><h1 class="style4">motto-captura</h1><h3 class="style…

    25. Error Line 51, Column > 80: XML Parsing Error: Premature end of data in tag body line 51.
      …asthead" class="style1"><h1 class="style4">motto-captura</h1><h3 class="style…

    26. Error Line 51, Column > 80: XML Parsing Error: Premature end of data in tag html line 1.
      …asthead" class="style1"><h1 class="style4">motto-captura</h1><h3 class="style…

    Wednesday, May 28, 2008 2:44 PM

All replies

  • xWeb creates valid XHTML 1.0 Transitional code by default. How did you create this document? I bet that at least parts of it were not created in xWeb.
    Wednesday, May 28, 2008 2:54 PM
  • EW does create compliant code.  It does not prevent you from starting with some other tools' non-compliant code, copying and pasting non-compliant code from somewhere else, or breaking what EW creates by editing code view incorrectly (but it will warn you about errors in code view).

    Also, in case you were under the impression that it did, clean up and HTML optimization will not automtically correct bad code if that's what you started with.

    How was this code created?
    Wednesday, May 28, 2008 4:05 PM