Hi Coolite,
The pages where I have your control fail XHTML Strict Validation on version 1.4:
Is there anything I can do? The rest of my site is compliant...
Here are the errors (all within the BDP span tag):
Normal
0
false
false
false
EN-GB
X-NONE
X-NONE
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Validation Output:
3 Errors
-
Line 79, Column 371:
document type does not allow element "link" here.…av0-4w2&amp;t=633554503980000000"></link><script type="text/javascript" s
✉
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 570, Column 292:
document type does not allow element "link" here.
…av0-4w2&amp;t=633554503980000000"></link><input name="ctl00$ContentPlaceH
✉
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 570, Column 553:
there is no attribute "border".
…age" class="bdpButton" alt="" border="10" src="/websites/ics5/www/ASPNET_Memb
✉
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.