Darstellungsprobleme

Thorsten_NE

Erdapfel
Registriert
23.01.07
Beiträge
5
Habe bisher keinen Browser gefunden der die folgende Homepage fehlerfrei darstellt. Bisher ist mir die einzig fehlerfreie Darstellung auf einem Windows-Rechner mit Internet-Explorer geglückt.

Hat jemand eine Browser-Alternative oder liegt es an der Codierung der Web-Seite?

http://www.bbv-jugend.de/
 

macchrissli

Celler Dickstiel
Registriert
21.05.05
Beiträge
803
liegt irgendwie am seltsamen code, wahrscheinlich hat das jemand nur mit internet explorer getestet und da siehts drauf aus, da der manche code sachen garnicht unterstützt, die allerdings hier falsch zu sein scheinen.
 

Paul-L

Jerseymac
Registriert
24.10.05
Beiträge
456
Also, an der Seite gibt es Unmengen an Verbesserungspotential, oder um es an diesem Tage mal anders auszudrücken: Da hat einer schlampig programmiert:

Zur Webseite selber - das CSS-File ist unten:

Below are the results of attempting to parse this document with an SGML parser.
  1. Error Line 1 column 0: 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.
    .
  2. Error Line 4 column 77: character data is not allowed here....//www.bbv-jugend.de/bilder/wappen.ico" /> 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).
    .
  3. Error Line 12 column 29: required attribute "TYPE" not specified.<script language="Javascript"> 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>.
    .
  4. Error Line 22 column 40: there is no attribute "TOPMARGIN".<body onload="open_window();" topmargin="0" leftmargin="0"> 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.
  5. Error Line 22 column 55: there is no attribute "LEFTMARGIN".<body onload="open_window();" topmargin="0" leftmargin="0">
    .
  6. Error Line 78 column 21: end tag for element "A" which is not open.escape(et_ref)+"'></a>"); } 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 occured in a script section of your document, you should probably read this.
    .
  7. Error Line 116 column 129: value of attribute "ALIGN" cannot be "CENTER"; must be one of "TOP", "MIDDLE", "BOTTOM", "LEFT", "RIGHT"....dth="0" frameborder="0" align="center"></iframe> The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.
    .
  8. Error Line 122 column 6: end tag for "DIV" 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.
    .
  9. Info Line 24 column 0: start tag was here.<div id="body">
Zum CSS-File:

5 body Die Eigenschaft scrollbar-base-color existiert nicht : #ffffdd

6 body Die Eigenschaft scrollbar-arrow-color existiert nicht : #000000

7 body Die Eigenschaft scrollbar-track-color existiert nicht : #ffff99

8 body Die Eigenschaft scrollbar-3dlight-color existiert nicht : #eeeeee

144 #navioben a Ungültige Nummer : margin nur 0 kann ein length sein. Nach der Zahl muß eine Einheit stehen. : 2px 2px 1px 2

... Also allein diese Probleme sorgen dafür, dass die Seite nicht richtig angeschaut werden kann.

Zudem würde ich mir immer Gedanken machen, wenn ich eine Webseite nur mit einem Browser anschauen kann, egal ob IE, oder Firefox, oder Safari: In so einem Fall bitte nicht auf die Browser schimpfen, sondern in den Spiegel schauen ;)

Für den nächsten Prüfvorgang bitte unter:

http://www.w3.org/

nachschauen, ob die Webseite passt.
 
Zuletzt bearbeitet:

manuel

Meraner
Registriert
19.08.04
Beiträge
233
Das liegt auf jeden Fall an der Seite, nicht an den Browsern. Die Seite wurde nur mit dem IE getestet, denn der stellt das korrekt dar.
 

PatrickB

Rhode Island Greening
Registriert
29.10.05
Beiträge
478
Auch eine W3C Validierung garantiert nie, dass der Internet Explorer die Sache auch richtig darstellt – sie garantiert nur für den Syntax und für das richtige Vokabular. Der Rest ist nunmal Interpretationssache. bzw. auch eigentlich nicht:

Internet Explorer legt es halt einfach anders (falsch) aus :)