Despite pre-purchase due diligence and assurances from IG, we're finding that many IG controls don't seem to generate XHTML 1.0 Transitional compliant code. IG claims like:
"XHTML Compliance - The default DOCTYPE for Web Forms in Visual Studio 2005 is XHTML 1.0 Transitional – and we have ensured that all Infragistics ASP.NET controls are compliant with this XHTML standard – empowering you to use either classic HTML 4 or the emerging XHTML 1.0 Transitional DOCTYPE." - https://es.infragistics.com/community/blogs
were part of our decision to use these controls.
Now, for the first time, we're working a project for a client that demands that each of our pages pass the XHTML 1.0 Transitional standard test at validator.w3.org. We're using release 2007.1 controls and several of them, including the UltraWebListBar control for ASP.NET 2.0 don't generate code that conforms to this standard. The w3.org tests report "errors" like this in the control-generated code, most of which are the result of Capitalization instead of capitalization in the attributes generated by the controls.
FROM THE W3.ORG validator:
Line 61, Column 44: there is no attribute "Cellpadding".
… id="UltraWebListbar1" Cellpadding<ERROR=0 CellSpacing=0 border="" borderstyle="N
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.
How do we get controls that actually do meet the XHTML 1.0 Transitional compliance that IG says they do? Or, is there a painless workaround. We're on a tight critical path.
Sorry for being so curt, but my boss is killing me.
Jason L.SmithSystems, Inc.