| Autor |
Beitrag |
AXMD
      
Beiträge: 4006
Erhaltene Danke: 7
Windows 10 64 bit
C# (Visual Studio 2019 Express)
|
Verfasst: So 06.02.05 17:13
Moin  !
Folgendes Problem: ich versuche gerade, meine HP etwas HTML-konformer zu gestalten, damit sie nicht in jedem Browser anders aussieht. Soweit so gut, aber ich find keine Eigenschaft von <frame> oder <frameset>, die es mir erlauben würde, den Abstand zwischen zwei Frames auf null Pixel zu setzen.
Auf meiner Homepage hab ich den ein oder zwei Pixel großen Abstand einfach vergrößert damit es so aussieht als wäre der weiße Zwischenraum Absicht.
Kann mir viell. jemand sagen, wie ich diesen weißen Rand HTML 4.01 konform verschwinden lassen kann?
Quelltext 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20:
| <html> <head> <title>DSTP Terminplaner Hilfe</title> <link rel="StyleSheet" href="tp_style.css"> </head> <frameset rows="120,5,*"> <frame src="top.html" scrolling="no" frameborder="0" marginwidth="0" marginheight="0" noresize> <frame src="empty.html" scrolling = "no" frameborder="0" marginwidth="0" marginheight="0"> <frameset cols="229,*"> <frame src="menu.html" scrolling="no" frameborder="0" marginwidth="15" marginheight="20" noresize> <frameset rows="*,12"> <frame src="welcome.html" name="Textfield" scrolling="auto" frameborder="0" marginwidth="15" marginheight="20" noresize> <frame src="copyrght.html" scrolling="no" frameborder="0" marginwidth="0" marginheight="0" noresize> </frameset> </frameset> <noframes> Sie benötigen einen Browser, der Frames unterstützt, um diese Seite ansehen zu können. </noframes> </frameset> </html> |
AXMD
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: So 06.02.05 17:34
Sorry, aber wieso hast du das drin??
Quelltext 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20:
| <html> <head> <title>DSTP Terminplaner Hilfe</title> <link rel="StyleSheet" href="tp_style.css"> </head> <frameset rows="120,5,*"> <frame src="top.html" scrolling="no" frameborder="0" marginwidth="0" marginheight="0" noresize> <frame src="empty.html" scrolling = "no" frameborder="0" marginwidth="0" marginheight="0"> <frameset cols="229,*"> <frame src="menu.html" scrolling="no" frameborder="0" marginwidth="15" marginheight="20" noresize> <frameset rows="*,12"> <frame src="welcome.html" name="Textfield" scrolling="auto" frameborder="0" marginwidth="15" marginheight="20" noresize> <frame src="copyrght.html" scrolling="no" frameborder="0" marginwidth="0" marginheight="0" noresize> </frameset> </frameset> <noframes> Sie benötigen einen Browser, der Frames unterstützt, um diese Seite ansehen zu können. </noframes> </frameset> </html> |
Ich hab mal in meinen alten "Frameseiten" gesucht (Jetzt verwende ich Tabellen mit falls nötig Inlineframes, ist sehr zu empfehlen.) und da sieht so ein Beispiel so aus:
Quelltext 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23:
| <html>
<head> <title>Blabla</title> </head>
<frameset framespacing="0" border="0" frameborder="0" rows="64,*,64"> <frame name="1" scrolling="no" noresize target="2" src="site4.htm"> <frameset cols="150,*"> <frame name="2" target="3" src="site5.htm"> <frame name="3" scrolling="auto" src="site3.htm"> </frameset> <frame name="4" scrolling="no" noresize target="2" src="site2.htm"> <noframes> <body topmargin="0" leftmargin="0">
<p>Your Browser does not support frames.</p>
</body> </noframes> </frameset>
</html> |
Vielleicht hilft's. 
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
AXMD 
      
Beiträge: 4006
Erhaltene Danke: 7
Windows 10 64 bit
C# (Visual Studio 2019 Express)
|
Verfasst: So 06.02.05 17:47
Nö  .
Schau jetzt mal auf meine HP; da sieht man den Abstand deutlich. Es gibt zwar im frameset das Attribut framespacing, das ich auf 0 setzen kann - das kennt aber nur der IE und das is auch nicht HTML4-konform
AXMD
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: So 06.02.05 19:36
Sorry, dass das jetzt so lange gedauert hat, aber ich war weg.
Ich hab nochmal nach meiner "Vorlage" eine kleine Frameseite erstellt und sie auf meinen Webspace geladen.
Link: www.rzuser.uni-heide...rig/AXMD%20Homepage/
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: So 06.02.05 20:29
Ich hab's!!
Glaub' ich zumindest!!
Meiner Meinung nach fehlt dir die framespacing="0"-Eigenschaft im <frameset>-Tag. Probier's mal aus!!

_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
AXMD 
      
Beiträge: 4006
Erhaltene Danke: 7
Windows 10 64 bit
C# (Visual Studio 2019 Express)
|
Verfasst: Mo 07.02.05 10:24
| AXMD hat folgendes geschrieben: | | Es gibt zwar im frameset das Attribut framespacing, das ich auf 0 setzen kann - das kennt aber nur der IE und das is auch nicht HTML4-konform |
(oberer Beitrag  )
AXMD
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: Mo 07.02.05 10:43
Okay, ich hätt's vielleicht nochmal lesen sollen, bevor ich poste, aber wer sagt das denn??
Gibbet da so'ne Liste wo das alles drin steht?? Dann stimmt die nämlich nicht so ganz!  Mit meinem Netscape Nav. 4.7 geht's auch. Und der ist schon saualt!!
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
AXMD 
      
Beiträge: 4006
Erhaltene Danke: 7
Windows 10 64 bit
C# (Visual Studio 2019 Express)
|
Verfasst: Mo 07.02.05 10:49
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: Mo 07.02.05 10:56
Also wenn ich da mal diese Testseite von mir checke, dann meint er, dass da gar nichts stimmt. Ich bezweifle stark, dass diese Seite wirklich versteht, was sie macht!
Diese komische Seite sagt: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: 43: 44: 45: 46: 47: 48: 49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: 62: 63: 64: 65: 66: 67: 68: 69: 70: 71: 72: 73: 74: 75: 76: 77: 78: 79: 80: 81: 82: 83: 84: 85: 86: 87: 88: 89: 90: 91: 92: 93: 94: 95: 96: 97: 98: 99: 100: 101: 102: 103: 104: 105: 106: 107: 108: 109: 110: 111: 112: 113: 114: 115: 116: 117: 118: 119: 120: 121: 122: 123: 124: 125: 126: 127: 128: 129: 130: 131: 132: 133: 134: 135: 136: 137: 138: 139: 140: 141: 142: 143: 144: 145: 146: 147: 148: 149: 150: 151: 152: 153: 154: 155: 156: 157: 158: 159: 160: 161: 162: 163: 164: 165: 166: 167: 168: 169: 170: 171: 172: 173: 174: 175: 176: 177: 178: 179: 180: 181: 182: 183: 184: 185: 186: 187: 188: 189: 190: 191: 192: 193: 194: 195: 196: 197: 198: 199: 200: 201: 202: 203: 204: 205: 206: 207: 208: 209: 210: 211: 212: 213: 214: 215: 216: 217: 218: 219: 220: 221: 222: 223: 224: 225: 226: 227: 228: 229: 230: 231: 232: 233: 234: 235: 236: 237: 238: 239: 240: 241: 242: 243: 244: 245: 246: 247: 248: 249: 250: 251: 252: 253: 254: 255: 256: 257: 258: 259: 260: 261: 262: 263: 264: 265: 266: 267: 268: 269: 270: 271: 272: 273: 274: 275: 276: 277: 278: 279: 280: 281: 282: 283: 284: 285: 286: 287: 288: 289: 290: 291: 292: 293: 294: 295: 296: 297: 298: 299: 300: 301: 302: 303: 304: 305: 306: 307: 308: 309: 310: 311: 312: 313: 314: 315: 316: 317: 318: 319: 320: 321: 322: 323: 324: 325: 326: 327: 328: 329: 330: 331: 332: 333: 334: 335: 336: 337: 338: 339: 340:
| Markup Validation Servicev0.6.7 Skip Navigation | Home About... News Docs Help & FAQ Feedback Link Checker Jump To: Results Source ListingParse Tree Address: Modified: Sun Feb 6 18:27:51 2005 Server: Apache/1.3.24 (Unix) DAV/1.0.3 Size: 616 Content-Type: text/html Encoding: utf-8 (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6 (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-13 (Baltic Rim) iso-8859-14 (Celtic) iso-8859-15 (Latin 9) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim) Doctype: HTML 4.01 Transitional (detect automatically) XHTML 1.1 XHTML Basic 1.0 XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset ISO/IEC 15445:2000 (ISO-HTML) HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 Errors: 20 Revalidate With Options: Show Source Outline Parse Tree ...no attributes Validate error pages Verbose Output Help on the options is available. No Character Encoding Found! Falling back to UTF-8.I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to reliably validate the document. I'm falling back to the "UTF-8" encoding and will attempt to perform the validation, but this is likely to fail for all non-trivial documents.
The sources I tried to find encoding information include:
The HTTP Content-Type field. The XML Declaration. The HTML "META" element. And I even tried to autodetect it using the algorithm defined in Appendix F of the XML 1.0 Recommendation.
Since none of these sources yielded any usable information, I will not be able to reliably validate this document. Sorry. Please make sure you specify the character encoding in use.
Specifying a character encoding is normally done in the web server configuration file or administration program. The W3C I18N Activity has collected a few tips on how to do this in popular web server implementations.
IANA maintains the list of official names for character sets and the WDG has some information to help you correctly specify the character encoding.
To quickly check whether the document would validate after addressing the missing character encoding information, you can use the "Encoding" form control (accesskey "2") earlier in the page to force an encoding override to take effect. "iso-8859-1" (Western Europe and North America) and "utf-8" (Universal, but not commonly used in legacy documents) are common encodings if you are not sure what encoding to choose.
No DOCTYPE Found! Falling Back to HTML 4.01 TransitionalA DOCTYPE Declaration is mandatory for most current markup languages and without one it is impossible to reliably validate this document. I am falling back to "HTML 4.01 Transitional" and will attempt to validate the document anyway, but this is very likely to produce spurious error messages for most non-trivial documents.
You should place a DOCTYPE declaration as the very first thing in your HTML document. For example, for a typical XHTML 1.0 document:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head> <title>Title</title> </head>
<body> <!-- ... body of document ... --> </body> </html> For XML documents, you may also wish to include an "XML Declaration" even before the DOCTYPE Declaration, but this is not well supported in older browsers. More information about this can be found in the XHTML 1.0 Recommendation.
The W3C QA Activity maintains a List of Valid Doctypes that you can choose from, and the WDG maintains a document on "Choosing a DOCTYPE".
DOCTYPE Fallback in effect! The DOCTYPE Declaration in your document was not recognized. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax. Validation has been performed using a default "fallback" Document Type Definition that closely resembles HTML 4.01 Transitional, but the document will not be Valid until you have corrected the problem with the DOCTYPE Declaration. This page is not Valid HTML 4.01 Transitional! Below are the results of attempting to parse this document with an SGML parser.
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 the HTML 4.01 Transitional 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.
✉
Line 7, column 15: there is no attribute "ROWS"
<frameset rows="64,*" framespacing="0" border="0" frameborder="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.
✉
Line 7, column 35: there is no attribute "FRAMESPACING"
<frameset rows="64,*" framespacing="0" border="0" frameborder="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.
✉
Line 7, column 46: there is no attribute "BORDER"
<frameset rows="64,*" framespacing="0" border="0" frameborder="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.
✉
Line 7, column 62: there is no attribute "FRAMEBORDER"
...et rows="64,*" framespacing="0" border="0" frameborder="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.
✉
Line 7, column 65: element "FRAMESET" undefined
...s="64,*" framespacing="0" border="0" frameborder="0">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 8, column 14: there is no attribute "NAME"
<frame name="Titel" scrolling="no" noresize target="Content" src="titel.html">
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.
✉
Line 8, column 32: there is no attribute "SCROLLING"
<frame name="Titel" scrolling="no" noresize target="Content" src="titel.html">
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.
✉
Line 8, column 46: "NORESIZE" is not a member of a group specified for any attribute
<frame name="Titel" scrolling="no" noresize target="Content" src="titel.html">
✉
Line 8, column 53: there is no attribute "TARGET"
<frame name="Titel" scrolling="no" noresize target="Content" src="titel.html">
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.
✉
Line 8, column 67: there is no attribute "SRC"
...tel" scrolling="no" noresize target="Content" src="titel.html">
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.
✉
Line 8, column 79: element "FRAME" undefined
...size target="Content" src="titel.html">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 9, column 17: there is no attribute "COLS"
<frameset cols="150,*">
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.
✉
Line 9, column 24: element "FRAMESET" undefined
<frameset cols="150,*">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 10, column 60: element "FRAME" undefined
<frame name="Content" target="Inhalt" src="content.html">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 11, column 26: element "FRAMESET" undefined
<frameset rows="*,49%">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 12, column 44: element "FRAME" undefined
<frame name="Inhalt" src="inhalt.html">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 13, column 82: element "FRAME" undefined
...html" scrolling="auto" target="_self">
You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
✉
Line 17, column 7: document type does not allow element "BODY" here
<body>
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).
✉
Line 25, column 6: end tag for "HTML" which is not finished
</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 (e.g. 'ul') which requires a child element (e.g. 'li') that you did not include. Hence the parent element is "not finished", not complete.
✉
Source Listing Below is the source input I used for this validation:
1: <html> 2: 3: <head> 4: <title>Homepagetitel</title> 5: </head> 6: 7: <frameset rows="64,*" framespacing="0" border="0" frameborder="0"> 8: <frame name="Titel" scrolling="no" noresize target="Content" src="titel.html"> 9: <frameset cols="150,*"> 10: <frame name="Content" target="Inhalt" src="content.html"> 11: <frameset rows="*,49%"> 12: <frame name="Inhalt" src="inhalt.html"> 13: <frame name="Copyright" src="copyright.html" scrolling="auto" target="_self"> 14: </frameset> 15: </frameset> 16: <noframes> 17: <body> 18: 19: <p>Your browser does not support frames.</p> 20: 21: </body> 22: </noframes> 23: </frameset> 24: 25: </html> Parse Tree You can also view this parse tree without attributes by selecting the appropriate option on the form.
AVERSION CDATA -//W3C//DTD HTML Fallback//EN <HTML> <HEAD> <TITLE> Homepagetitel </TITLE> </HEAD> AROWS CDATA 64,* AFRAMESPACING CDATA 0 ABORDER CDATA 0 AFRAMEBORDER CDATA 0 <FRAMESET> ANAME CDATA Titel ASCROLLING CDATA no ATARGET CDATA Content ASRC CDATA titel.html <FRAME> ACOLS CDATA 150,* <FRAMESET> ANAME CDATA Content ATARGET CDATA Inhalt ASRC CDATA content.html <FRAME> AROWS CDATA *,49% <FRAMESET> ANAME CDATA Inhalt ASRC CDATA inhalt.html <FRAME> ANAME CDATA Copyright ASCROLLING CDATA auto ATARGET CDATA _self ASRC CDATA copyright.html <FRAME> </FRAME> </FRAME> </FRAMESET> </FRAME> </FRAMESET> <NOFRAMES> <BODY> <P> Your browser does not support frames. </P> </BODY> </NOFRAMES> </FRAME> </FRAMESET> </HTML>
Feedback: The W3C Validator Team Date: 2004/07/21 10:24:06 Copyright © 1994-2004 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. |
Ne, jetzt mal im Ernst. Wenn's doch mit NN4.7 funktioniert. Probier halt mal den NN7, Firefox, Mozilla und Opera aus und dann schreib auf deine Seite einfach bei diesem "für 1280*1024 optimiert" noch "getestet mit ..." dazu. 
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
AXMD 
      
Beiträge: 4006
Erhaltene Danke: 7
Windows 10 64 bit
C# (Visual Studio 2019 Express)
|
Verfasst: Mo 07.02.05 11:05
| WeBsPaCe hat folgendes geschrieben: | | Ich bezweifle stark, dass diese Seite wirklich versteht, was sie macht! |
Also ich glaube, dass du nicht weißt, was W3C ist. Solltest ansonsten vielleicht mal diese HTML4-Referenz oder alternativ [url] www.w3c.org[/url] besuchen
AXMD
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: Mo 07.02.05 11:20
Ich zitiere mich:
| WeBsPaCe hat folgendes geschrieben: | | Ne, jetzt mal im Ernst. Wenn's doch mit NN4.7 funktioniert. Probier halt mal den NN7, Firefox, Mozilla und Opera aus und dann schreib auf deine Seite einfach bei diesem "für 1280*1024 optimiert" noch "getestet mit ..." dazu. |
Mir ist schon klar, dass diese Eigenschaft dann nicht "genormt" ist. Aber wenn sie in wirklich allen (nicht getestet, vermute es aber stark - siehe letzten Beitrag) gängigen Browsern drinne ist, wieso dann nicht verwenden... 
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
AXMD 
      
Beiträge: 4006
Erhaltene Danke: 7
Windows 10 64 bit
C# (Visual Studio 2019 Express)
|
Verfasst: Mo 07.02.05 11:33
Firefox kennt die Eigenschaft beispielsweise nicht...
AXMD
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: Mo 07.02.05 11:35
| AXMD hat folgendes geschrieben: | | Firefox kennt die Eigenschaft beispielsweise nicht... |
Gut, dann hab ich mich geirrt. Sorry.
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
WeBsPaCe
      
Beiträge: 2322
Erhaltene Danke: 1
FireFox 3, Internet Explorer 6 SP1
D1, D3Prof, D6Pers, D7Pers+Indy, VisualStudio Express
|
Verfasst: Mi 09.02.05 18:29
Wie zeigt es denn Firefox an?? Weil ich sehe gerade, dass du's ja doch übernommen hast!! 
_________________ Steht der Bauer im Gemüse, hat er später grüne Füße.
|
|
|