naja bei deinem link den du angibt habe ich keine meldung vom body in der art
da habe ich andere
Validator message export for "http://www.rc-boote.at/upload/boby/speedcalc2_multi.php":
Generated by CSE HTML Validator Professional v6.53 (
http://www.htmlvalidator.com/)
1. Message: [73] WCAG 1.0 accessibility checking is disabled.
2. Message: [73] Section 508 accessibility checking is disabled.
3. Message in line 7 at character 2: [111] Tip - A good title is very important. Use many keywords in your title tag but make it readable. This is good for search engine rankings and when the page is bookmarked. Example:
Download CSE HTML Validator - Powerful HTML and Link Checking Software for Windows.
4. Message in line 7 at character 8: [8] This document's title contains only 1 word. It may be inadequate for search engine purposes. A good title is important to your search engine rankings and listings. AI Internet Solutions recommends a title that is 5-15 words in length and that contains a relevant and descriptive phrase.
5. Error in line 9 at character 2: The "script" tag was found, but it is not valid due to where it is used. This element may be contained in "body" and "head". This element may not be contained in "frameset". The tag is currently not contained in an element that allows its use.
6. Error in line 10 at character 1: Text is contained in a "html" tag. Because it is contained in this tag, it must also be contained in one of the following elements: "body" "head" "noframes".
7. Message in line 24 at character 6: [9] The "font" element and all of its attributes are deprecated in HTML 4.01 and XHTML in favor of using style sheets (use the CSS "color", "font", "font-family", "font-size", and other font properties instead).
8. Message in line 26 at character 7: HTML 4.01 and XHTML allow the "name" attribute with the "form" element for backward compatibility. However, the "id" attribute should be used to identify elements. Previously, HTML 4.0 did not allow the "name" attribute with the "form" element. It is recommended that both "name" and "id" attributes be used when using the "form" element. The values for both of these attributes should be identical.
9. Message in line 27 at character 3: Consider using the "width" attribute with the "table" element. This is considered to be good style and can cause the table and page to render faster. Note that this is not a deprecated attribute in HTML 4.01 nor XHTML 1.0. It's also a valid XHTML 1.1 attribute.
10. Message in line 27 at character 3: [5] The "table" element is an official HTML 4.01 and XHTML element but may not be supported by older or nongraphical browsers. Furthermore, nongraphical browsers that do support tables may not support them the way that you expect. However, most browsers used today should support this element.
11. Message in line 27 at character 32: [9] The "align" and "bgcolor" attributes for the "table" element are deprecated in HTML 4.01 and XHTML in favor of using style sheets. Instead of the "bgcolor" attribute, consider using the CSS "background-color" property instead.
12. Message in line 29 at character 23: [9] The "bgcolor" attribute for the "td" and "th" elements is deprecated in HTML 4.01 and XHTML in favor of using style sheets. Consider using the CSS "background-color" property instead of the "bgcolor" attribute.
13. Message in line 30 at character 5: The "strong" element should be used instead of the "b" element when you want to denote strong emphasis. The "b" element should only be used when you want bold typeface but do not want strong emphasis. Many web authors use the "b" element when the "strong" element would be more appropriate.
14. Message in line 37 at character 52: The "em" element (for emphasized text) or the "cite" element (for citations) may be more appropriate than the "i" element. Use the "i" element only if text is in italics by convention. Many web authors use the "i" element when the "em" element would be more appropriate.
15. Error in line 47 at character 40: The "font" tag must have an end tag but the end tag was not found.
16. Error in line 50 at character 7: Found the character '<' while looking for '>'. The character '>' must appear before another '<'. If you actually want to use this character in the text portion of your document, then you should use the character entity reference "<".
17. Error in line 50 at character 8: The end tag for "font" (opened in line 47) should appear before the end tag for "td" (nesting error).
18. Warning in line 51 at character 5: [30] The "td" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "td" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "td" tag; 2. Eliminate the "td" tag; or 3. Reorder the "td" and "font" tags.
19. Message in line 62 at character 6: No option was selected using the "selected" attribute in this "select" tag. Because browsers behave differently, it is recommended that you use the "selected" attribute in an "option" tag to explicitly specify a default pre-selected option.
20. Warning in line 65 at character 4: [30] The "tr" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "tr" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "tr" tag; 2. Eliminate the "tr" tag; or 3. Reorder the "tr" and "font" tags.
21. Warning in line 66 at character 5: [30] The "td" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "td" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "td" tag; 2. Eliminate the "td" tag; or 3. Reorder the "td" and "font" tags.
22. Warning in line 69 at character 4: [30] The "tr" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "tr" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "tr" tag; 2. Eliminate the "tr" tag; or 3. Reorder the "tr" and "font" tags.
23. Warning in line 70 at character 5: [30] The "td" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "td" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "td" tag; 2. Eliminate the "td" tag; or 3. Reorder the "td" and "font" tags.
24. Warning in line 74 at character 5: [30] The "td" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "td" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "td" tag; 2. Eliminate the "td" tag; or 3. Reorder the "td" and "font" tags.
25. Warning in line 77 at character 3: [30] The "p" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "p" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "p" tag; 2. Eliminate the "p" tag; or 3. Reorder the "p" and "font" tags.
26. Warning in line 79 at character 2: [30] The "hr" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "hr" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "hr" tag; 2. Eliminate the "hr" tag; or 3. Reorder the "hr" and "font" tags.
27. Warning in line 81 at character 2: [30] The "hr" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "hr" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "hr" tag; 2. Eliminate the "hr" tag; or 3. Reorder the "hr" and "font" tags.
28. Warning in line 85 at character 158: [30] The "hr" tag is contained in a "font" tag (which was opened in line 47). This may be acceptable for some browsers (such as Internet Explorer and Netscape), but HTML 4.01 and XHTML do not allow this. It may also cause problems or unexpected page rendering for more compliant browsers such as Opera and Mozilla. Possible solutions: 1. Close the "font" tag before using the "hr" tag. Depending on the correct usage of the closed tag, you may be able to reopen it after using the "hr" tag; 2. Eliminate the "hr" tag; or 3. Reorder the "hr" and "font" tags.
29. Comment: This program can help you make your web pages more accessible. An accessible page is one that more individuals can use, such as individuals who are blind or deaf. It can also increase the usefulness of your web page for individuals who browse the web using slower devices like older computers or wireless devices like cell phones and PDAs. An accessible web site makes good business sense (and possibly good legal sense as well). You can enable or disable accessibility checking in the Validator Engine Options.
30. Comment: You can ignore the nesting errors by turning off the option to check HTML tag nesting. However, it is recommended that you leave this feature enabled. This option is in CSE HTML Validator's Validator Engine Options.
31. Comment: Possibly misspelled words (85, 70 unique): Antriebs (1x), Antriebsauslegung (1x), Anwendung (1x), Aufgrund (1x), Auslegung (1x), bei (1x), Berechnung (1x), Berechungen (1x), boote.at (1x), Danke (1x), Danz (1x), diesen (1x), document.SpeedForm.F (1x), durch (1x), Durchmesser (1x), eines (1x), empfehlen (1x), entstanden (1x), errechneten (1x), etwaige (1x), Faktor (1x), FECalc (1x), geben (1x), Geschwindigkeit (1x), grobe (1x), Haftung (1x), handelt (1x), Heiko (1x), hier (1x), ist (1x), keine (1x), Lastdrehzahl (1x), Leerlaufdrehzahl (1x), mit (1x), Modell (1x), Motordaten (1x), Näherungswerte (1x), Orientierung (1x), Parametereingabe (1x), Parametern (1x), Propellerdaten (1x), Raziel (1x), Rechner (1x), Rennboot (1x), Rennbooten (1x), Schäden (1x), ShowFactor (1x), sich (1x), sind (1x), Steigung (1x). List limited to first 50 unique words.
32. Comment: HTML 4.01 Transitional document detected.
33. Comment: [111] Tip - Do not use hidden text, small text, comments, popular but unrelated words, etc. to try to 'cheat' to gain better search engine rankings. This is dishonest and some search engines may lower a page's rank for trying to 'cheat'.
34. Comment: [8]
should be used in the "head" section to provide a brief description of what is contained on this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu and/or from the Tag Inserter.
35. Comment: [8]
should be used in the "head" section to provide a list of keywords that are relevent to this page. This information is used by many search engines when indexing a site. If you are using HTML Validator's integrated editor, then you can add this from the Tags menu and/or from the Tag Inserter.
36. Comment: An ICRA label (a rating "meta" tag) was not found in the "head" section of this document. Browsers that are enabled with this rating system may not display documents that have not been labelled. If you have labelled this document by rating the section (directory) in which it is found, or if your site is a personal web space on a large Internet Service Provider, it is still recommended that you include the rating "meta" tag on all of your pages for performance reasons. For more information, please visit
http://www.icra.org/.
37. Comment: [10] CSE HTML Validator Std/Pro allows you to disable certain messages (like this example message) and groups of related messages by disabling flags. For instance, the [10] at the beginning of this message indicates that you can disable this message by disabling validator flag 10. If you are using HTML Validator's integrated editor, then you can simply use your mouse on this message to open the context menu (usually done by right-clicking the mouse on this message) and select 'Disable Flag 10' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
38. Comment: CSE HTML Validator Std/Pro allows you to disable many messages on an individual basis without using flags. For instance, you can disable this message by using HTML Validator's integrated editor to open the context menu for this message (usually done by right-clicking the mouse on this message) and selecting 'Options for this Message->Disable Message' to disable this message. For more information about disabling messages, please look at the Configuration section in the documentation.
39. Comment: 3915 bytes
2.7s@14.4Kbps 1.4s@28.8 0.8s@50 0.6s@64 0.3s@128 0.1s@384 0.1s@512 0.1s@768 0.0s@1.5Mbps 0.0s@10Mbps.
40. Comment: 0.08s, 5 errors, 10 warnings, 13 messages, 12 validator comments, 87 lines, 82 tags (63 closed), 0 document comments, 10 entities, 219 programs run.
ich denke du hast das mit dem body auch nur wenn es in der anypage ist und dann sind da 2 body s
, spinne
Forum Index
Support
Problem bei ANYPAGE
