Jeg har forsøget at validere siden, men er ikke helt sikker på hvordan jeg skal få rettet fejlene og evt. angive placeringer osv vha. CSS. Er det noget I kan hjælpe med?
Koden er nu som følgende:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"
http://www.w3.org/TR/html4/strict.dtd"><?
$pageid = $_GET['pageid'];
?>
<html>
<head>
<title>Ny side</title>
<link rel="stylesheet" type="text/css" href="style.css">
</head>
<body>
<p align="center">
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" id="main">
<tr>
<td>
<table border="0" width="750">
<tr>
<td background="pictures/design/top.jpg" height="150" width="750" colspan="3">
</td>
</tr>
<td width="150">
<p align="center">
<br>
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse" bordercolor="#111111" width="140" id="menu">
<tr>
<td>
<?
include("menu.php");
?>
</td>
</tr>
</table>
</p>
<table border="0" height="100%">
<tr>
<td height="100%">
</td>
</tr>
</table>
</td>
<td width="600">
<br>
<p align="center">
<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="590" id="indhold">
<tr>
<td>
<?
if($pageid == "1"){ include("main/forside.php");
}
else if($pageid == "2"){ include("main/09kg.php");
}
else if($pageid == "3"){ include("main/918kg.php");
}
else if($pageid == "4"){ include("main/936kg.php");
}
else if($pageid == "5"){ include("main/1536kg.php");
}
else { include("main/forside.php");
}
?>
</td>
</tr>
</table>
</p>
<table border="0" height="100%">
<tr>
<td height="100%">
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td width="750" colspan="3">
<?
include("bund.php");
?>
</td>
</tr>
</table>
</td>
</tr>
</table>
</p>
</body>
</html>
Og valideringsfejlene er angivet til:Notes and Potential Issues
The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.
1.
Warning No Character Encoding Found! Falling back to windows-1252.
None of the standards sources gave any information on the character encoding labeling for this document. Without encoding information it is impossible to reliably validate the document. As a fallback solution, the "windows-1252" encoding was used to read the content and attempt to perform the validation, but this is likely to fail for all non-trivial documents.
Before defaulting to windows-1252 the validator also tried to read the content with the following encoding(s), without success: UTF-8.
Read the FAQ entry on character encoding for more details and pointers on how to fix this problem with your document.
2.
Info No Character encoding declared at document level
No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.
See this tutorial on character encoding for techniques and explanations.
↑ Top
Validation Output: 15 Errors
1. Error Line 15, Column 10: Attribute "ALIGN" is not a valid attribute. Did you mean "align"?
<p align="center">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
2. Error Line 16, Column 97: Attribute "BORDERCOLOR" is not a valid attribute
…der-collapse: collapse" bordercolor="#111111" id="main">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
3. Error Line 22, Column 17: Attribute "BACKGROUND" is not a valid attribute. Did you mean "background"?
<td background="pictures/design/top.jpg" height="150" width="750" colspan="3">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
4. Error Line 22, Column 50: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
<td background="pictures/design/top.jpg" height="150" width="750" colspan="3">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
5. Error Line 22, Column 62: Attribute "WIDTH" is not a valid attribute. Did you mean "width"?
…ckground="pictures/design/top.jpg" height="150" width="750" colspan="3">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
6. Error Line 28, Column 17: document type does not allow element "TD" here; assuming missing "TR" start-tag
<td width="150">
✉
7. Error Line 38, Column 15: Attribute "BGCOLOR" is not a valid attribute. Did you mean "bgcolor"?
<td bgcolor="#7a9294" width="100%" colspan="3"><p align="center"><b>Navigation
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
8. Error Line 45, Column 3: element "U" undefined. Did you mean "u"?
<u>Recaro stole</u><br>
✉
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),
* by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
* by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
9. Error Line 56, Column 4: end tag for element "P" which is not open
</p> </td>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
10. Error Line 59, Column 5: end tag for element "P" which is not open
</p>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
11. Error Line 63, Column 27: Attribute "HEIGHT" is not a valid attribute. Did you mean "height"?
<table border="0" height="100%">
✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
12. Error Line 79, Column 124: ID "AUTONUMBER1" already defined
…dercolor="#111111" width="100%" id="AutoNumber1">
✉
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
13. Info Line 35, Column 123: ID "AUTONUMBER1" first defined here
…rdercolor="#111111" width="100%" id="AutoNumber1">
14. Error Line 92, Column 4: end tag for element "P" which is not open
</p>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
15. Error Line 96, Column 5: end tag for element "P" which is not open
</p>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
16. Error Line 120, Column 4: end tag for element "P" which is not open
</p>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.
If this error occurred in a script section of your document, you should probably read this FAQ entry.
