Autor stefan
Datum 30.12.2006 19:17
Beiträge: Bitte korrigiere doch erstmal evt. die "paar" Fehler auf der Seite :wink: Dann Frage welche IE Version meinst du; Weil die verhalten sich unterschiedlich.

1. Warning in line 11 at character 18: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

2. Warning in line 12 at character 1: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

3. Warning in line 12 at character 145: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

4. Warning in line 13 at character 1: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

5. Warning in line 16 at character 1: [HTML Tidy] <link> inserting "type" attribute

6. Warning in line 23 at character 3: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, consider putting the style information in an external style sheet. The next best option for XHTML documents is to not put the style information in a comment because this is technically not what you want even though it may work with today's browsers.

7. Warning in line 32 at character 42: Because of issues with the Netscape implementation of JavaScript when language="JavaScript1.2" is explicitly requested, it is usually best to not explicitly set language="JavaScript1.2". Furthermore, relying on the nonconforming JavaScript behavior of Netscape when JavaScript1.2 is specified is not recommended. It is recommended that something else be specified for "language" or that the deprecated "language" attribute be removed altogether and the standards compliant "type" attribute be used instead, like type="text/javascript". This message is displayed only once when "JavaScript1.2" is first used.

8. Warning in line 33 at character 2: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, AI Internet Solutions recommends putting the script (especially longer scripts) in an external file and using the "src" attribute to specify the external file. The next best option for XHTML documents would be to not put the script content in a comment and to disregard pre HTML 3.2 browsers.

9. Warning in line 50 at character 72: [HTML Tidy] <img> attribute "height" has invalid value "auto"

10. Warning in line 50 at character 150: (Accessibility->General Accessibility) This alt text may be too short to be meaningful. Consider a longer and better description of the object. This alt text is only 4 characters long and should probably be lengthened.

11. Warning in line 50 at character 150: (Accessibility->General Accessibility) Alt text should be a short description of the image/applet or describe its functional purpose. It should be helpful and useful; "logo" is unlikely to be helpful and useful. Consider providing better alt text. For example, include the fully spelled out company name in the alt text, as in "AI Internet Solutions logo".

12. Error in line 50 at character 176: The "height" attribute has an invalid attribute value "auto". Try using one of the following values: a percent, a positive integer, or "0" (zero).

13. Warning in line 65 at character 1: [HTML Tidy] <table> lacks "summary" attribute

14. Warning in line 73 at character 2: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) Style sheets should be used to control layout and presentation [P2, 3.3]. The element you've used ("small") is a presentational element. Presentational elements include "font", "b", "i", "big", "small", and others. For presentation, consider using style sheets (CSS) instead. Use HTML elements only for content and structure and not for layout and presentation. Use the "em" and "strong" elements for structural emphasis. This message is displayed only once.

15. Warning in line 76 at character 1: [HTML Tidy] <form> proprietary attribute "autocomplete"

16. Error in line 76 at character 129: [nsgmls] there is no attribute "autocomplete"

17. Error in line 122 at character 10: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 1)) [70] The "iframe" element requires the "title" attribute to facilitate frame identification and navigation. Frame titles must be meaningful. For example, "Table of Contents", "Where the content is displayed", and "Sitewide navigation bar" (or simply "Navigation"). [P1, 12.1]

18. Error in line 122 at character 10: (Accessibility->Section 508 Accessibility Standards) [70] The "iframe" element requires the "title" attribute to facilitate frame identification and navigation. Frame titles must be meaningful. For example, "Table of Contents", "Where the content is displayed", and "Sitewide navigation bar" (or simply "Navigation"). [Section 1194.22 (i)]

19. Warning in line 122 at character 22: [64] An invalid character reference was found in the "src" attribute value. Often this is because the ampersand character was not properly encoded as the entity "&amp;". Other causes of invalid references are misspelled entity names and missing semicolons.

20. Warning in line 122 at character 68: [HTML Tidy] unescaped & or unknown entity "&o"

21. Error in line 122 at character 69: [nsgmls] general entity "o" not defined and no default entity

22. Warning in line 122 at character 72: [HTML Tidy] unescaped & or unknown entity "&p"

23. Error in line 122 at character 73: [nsgmls] general entity "p" not defined and no default entity

24. Warning in line 122 at character 77: [HTML Tidy] unescaped & or unknown entity "&l"

25. Error in line 122 at character 78: [nsgmls] general entity "l" not defined and no default entity

26. Warning in line 122 at character 83: [HTML Tidy] unescaped & or unknown entity "&f"

27. Error in line 122 at character 84: [nsgmls] general entity "f" not defined and no default entity

28. Warning in line 132 at character 119: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user [P2, 10.1]. Avoid using target="_blank" because spawning a new window can be confusing and disorienting to the user. If a new window must be spawned, then it is recommended that it be indicated in the link description, such as by using the text "new window" somewhere in the "title" attribute value (recommended) or by adding "(new window)" to the link description. This message is displayed up to 3 times.

29. Warning in line 132 at character 254: (Accessibility->General Accessibility) This alt text may be too short to be meaningful. Consider a longer and better description of the object. This alt text is only 7 characters long and should probably be lengthened.

30. Warning in line 141 at character 27: (Styles->General) It is recommended that a generic font family name be specified as the last font family name. If the preceding font family names are not available then the browser should fall back to the generic font family name. The generic font family names are serif, sans-serif, cursive, fantasy, and monospace. Be sure not to use quotes around generic font family names.

31. Warning in line 156 at character 1: [HTML Tidy] <div> attribute "id" has invalid value "1;3"

32. Error in line 156 at character 38: [nsgmls] value of attribute "id" invalid: "1" cannot start a name

33. Error in line 156 at character 38: An "id" attribute value must begin with a letter (A-Z or a-z) and consist of the following characters: (A-Z), (a-z), (0-9), hyphens (-), underscores (_), colons (:), and periods (.). Note that spaces are not allowed.

34. Warning in line 157 at character 1: [HTML Tidy] <table> attribute "bgcolor" lacks value

35. Warning in line 157 at character 1: [HTML Tidy] <table> lacks "summary" attribute

36. Warning in line 157 at character 1: [HTML Tidy] <table> proprietary attribute "bordercolor"

37. Warning in line 157 at character 85: (Grouped->General Compatibility) The "bordercolor", "bordercolordark", "bordercolorlight", "frame", or "rules" attribute has been used. In order for any of these attributes to work, it is necessary that the "border" attribute (for example, "border=1") also be used so that the border will be displayed.

38. Error in line 157 at character 97: [nsgmls] there is no attribute "bordercolor"

39. Error in line 157 at character 145: The hexadecimal color value for the "bgcolor" attribute is missing the '#' character. Use bgcolor="#".

40. Warning in line 159 at character 7: [HTML Tidy] <td> proprietary attribute "background"

41. Error in line 159 at character 51: [nsgmls] there is no attribute "background"

42. Warning in line 160 at character 7: [HTML Tidy] <td> proprietary attribute "background"

43. Warning in line 160 at character 156: The following typeface was not recognized (check spelling): "MS Arial".

44. Warning in line 163 at character 7: [HTML Tidy] <td> attribute "bgcolor" lacks value

45. Error in line 163 at character 30: The hexadecimal color value for the "bgcolor" attribute is missing the '#' character. Use bgcolor="#".

46. Warning in line 164 at character 7: [HTML Tidy] <td> attribute "bgcolor" lacks value

47. Error in line 164 at character 32: The hexadecimal color value for the "bgcolor" attribute is missing the '#' character. Use bgcolor="#".

48. Warning in line 170 at character 17: [HTML Tidy] <font> attribute "color" has invalid value "#000"

49. Error in line 170 at character 30: The "color" attribute has an invalid attribute value "#000". Try using one of the following values: one of the 16 basic color names, an X11 color name, a six digit hexadecimal number in the form #HHHHHH, or a system/UI color.

50. Warning in line 192 at character 94: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

51. Warning in line 192 at character 210: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

52. Warning in line 192 at character 211: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

53. Warning in line 192 at character 314: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

54. Warning in line 192 at character 315: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

55. Warning in line 192 at character 318: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

56. Warning in line 192 at character 325: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

57. Warning in line 192 at character 476: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

58. Warning in line 192 at character 477: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

59. Warning in line 192 at character 605: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

60. Warning in line 192 at character 606: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

61. Warning in line 192 at character 609: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

62. Warning in line 205 at character 70: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Kommentare?" has already been used to link to a different resource (http://www.scoutweb.de/opn/system/article/index.php?sid=6). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1]

63. Warning in line 205 at character 94: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

64. Warning in line 205 at character 210: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

65. Warning in line 205 at character 211: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

66. Warning in line 205 at character 314: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

67. Warning in line 205 at character 315: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

68. Warning in line 205 at character 318: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

69. Warning in line 205 at character 325: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

70. Warning in line 205 at character 476: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

71. Warning in line 205 at character 477: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

72. Warning in line 205 at character 605: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

73. Warning in line 205 at character 606: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

74. Warning in line 205 at character 609: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

75. Warning in line 219 at character 70: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Kommentare?" has already been used to link to a different resource (http://www.scoutweb.de/opn/system/article/index.php?sid=6). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1]

76. Warning in line 219 at character 94: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

77. Warning in line 219 at character 210: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

78. Warning in line 219 at character 211: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

79. Warning in line 219 at character 314: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

80. Warning in line 219 at character 315: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

81. Warning in line 219 at character 318: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

82. Warning in line 219 at character 325: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

83. Warning in line 219 at character 476: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

84. Warning in line 219 at character 477: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

85. Warning in line 219 at character 605: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

86. Warning in line 219 at character 606: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

87. Warning in line 219 at character 609: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

88. Warning in line 233 at character 70: (Accessibility->Web Content Accessibility Guidelines 1.0 (Priority 2)) The link text "Kommentare?" has already been used to link to a different resource (http://www.scoutweb.de/opn/system/article/index.php?sid=6). If more than one link on a page shares the same link text, then those links should point to the same resource. If two or more links refer to different resources but share the same link text, then specify different values for the "title" attribute of the "a" element to distinguish the links. [P2, 13.1]

89. Warning in line 233 at character 94: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

90. Warning in line 233 at character 210: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

91. Warning in line 233 at character 211: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

92. Warning in line 233 at character 314: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

93. Warning in line 233 at character 315: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

94. Warning in line 233 at character 318: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

95. Warning in line 233 at character 325: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

96. Warning in line 233 at character 476: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

97. Warning in line 233 at character 477: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

98. Warning in line 233 at character 605: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

99. Warning in line 233 at character 606: Found the character '<' in a '<!--' comment. If '<' indicates the start of another tag, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '<' in a strict comment.

100. Warning in line 233 at character 609: Found the character '>' in a '<!--' comment. Comments beginning with '<!--' must end with '-->', not '>'. If '>' indicates the end of the comment, this is an error, otherwise it is not, but it may be dangerous with some browsers to use the character '>' in a strict comment.

101. Warning in line 255 at character 1: [HTML Tidy] <table> lacks "summary" attribute

102. Warning in line 316 at character 2: In XHTML documents, style and script content must not be in a comment because it technically means that the browser will see it as a comment and not as actual style or script content (though browsers are currently forgiving about this). However, not using comments makes your document less compatible with pre HTML 3.2 browsers (but most browsers now in use are HTML 3.2+ compatible). For maximum compatibility, AI Internet Solutions recommends putting the script (especially longer scripts) in an external file and using the "src" attribute to specify the external file. The next best option for XHTML documents would be to not put the script content in a comment and to disregard pre HTML 3.2 browsers.

103. Warning in line 333 at character 24: [HTML Tidy] <table> lacks "summary" attribute

104. Warning in line 357 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

105. Warning in line 357 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

106. Warning in line 362 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

107. Warning in line 362 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

108. Warning in line 367 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

109. Warning in line 367 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

110. Warning in line 374 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

111. Warning in line 374 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

112. Warning in line 379 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

113. Warning in line 379 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

114. Warning in line 384 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

115. Warning in line 384 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

116. Warning in line 389 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

117. Warning in line 389 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

118. Warning in line 394 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

119. Warning in line 394 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

120. Warning in line 399 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

121. Warning in line 399 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

122. Warning in line 404 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

123. Warning in line 404 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

124. Warning in line 411 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

125. Warning in line 411 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

126. Warning in line 416 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

127. Warning in line 416 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

128. Warning in line 421 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

129. Warning in line 421 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

130. Warning in line 426 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

131. Warning in line 426 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

132. Warning in line 431 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

133. Warning in line 431 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

134. Warning in line 436 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

135. Warning in line 436 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

136. Warning in line 441 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

137. Warning in line 441 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

138. Warning in line 448 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

139. Warning in line 448 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

140. Warning in line 453 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

141. Warning in line 453 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

142. Warning in line 458 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

143. Warning in line 458 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

144. Warning in line 463 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

145. Warning in line 463 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

146. Warning in line 468 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

147. Warning in line 468 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

148. Warning in line 473 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

149. Warning in line 473 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

150. Warning in line 478 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

151. Warning in line 478 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

152. Warning in line 485 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

153. Warning in line 485 at character 145: (Styles->General) The "background" shorthand property and the "background-repeat" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-repeat" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to type.

154. Warning in line 490 at character 60: (Styles->General) The "background" shorthand property and the "background-image" property have both been used. The "background" shorthand property already defines the following properties: "background-attachment", "background-color", "background-image", "background-position", and "background-repeat". Therefore, the "background-image" property has been defined twice. Use of the "background" shorthand property is encouraged over the other background properties because it's more widely supported and it's quicker to typ


Diese Seite drucken
Diese Seite schließen

Dieser Artikel kommt von: OpenPHPNuke - das Open Source CMS
http://www.openphpnuke.info/