1 Reply Latest reply on Jun 19, 2007 10:30 AM by DC_Eric

    Crappy in Firefox

    Level 7
      Hello everybody,
      my site www.azubel.com looks fine in IE, but crappy in Firefox. Are there
      critical items that should be taken care of? Or is it something general and
      the whole code must be looked at?



        • 1. Re: Crappy in Firefox
          DC_Eric Level 1
          Your pages don't validate. Below are the errors and pay special attention to #5 I believe this is why your site looks different in FF

          Below are the results of attempting to parse this document with an SGML parser.

          1. Error Line 5 column 79: character data is not allowed here.

          ...vpGLidhzMjid2K0hGNZyl+yCDEnA+KC4yk=" />

          You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>) or forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes).

          2. Error Line 117 column 254: required attribute "ALT" not specified.

          ...7" height="17" border="0" id="entrar"></a></td>

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

          3. Error Line 125 column 48: document type does not allow element "FORM" here; missing one of "TH", "TD" start-tag.

          <tr><form name="form1" method="post" action="">

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

          4. Error Line 126 column 27: document type does not allow element "TD" here.

          <td class="celdaForm"><img src="images/home/usr.gif" alt="" width="67" hei

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

          5. Error Line 131 column 15: end tag for "TR" which is not finished.


          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, <head> generally requires a <title>, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.