www.teamdev.com

This Question is Answered

2 "helpful" answers available (2 pts)
4 Replies Last post: Jul 30, 2008 8:08 PM by Oliver Nelson  
Click to view Oliver Nelson's profile   5 posts since
Jul 29, 2008

Jul 30, 2008 11:48 AM

W3C validation problem: <nobr> in DataTable component

Dear TeamDev Team,


the tag <nobr> is not standard HTML but used in the DataTable component for column headers.

Example from QuipuKit demo page:

<td rowspan="2"><nobr>Institution Name<img src="../images/treetable/sort_a.gif" style="margin-left: 5px" /></nobr></td>

My suggestion would be to use styles like here:

<td rowspan="2" style="white-space:nowrap;">Institution Name</td>

This works with HTML 4.1 and XHTML 1.0 and leads to less validation errors with the W3C Validator.

If you change this behaviour - would that already be part of QuipuKit 1.6 or a later version?

Kind regards

Oliver Nelson

Click to view Dmitry Pikhulya's profile TeamDev Ltd. 147 posts since
Jan 5, 2007
1. Jul 30, 2008 5:40 PM in response to: Oliver Nelson
Re: W3C validation problem: <nobr> in DataTable component
Hello Oliver,

We've implemented this change and it will be available with QuipuKit 1.6 release. Though there was one issue: assigning "white-space: nowrap" on table cells doesn't work reliably under Internet Explorer, but we've been able to fix this by applying the style to an encompassing tag, which works fine in IE.

Please also let us know why it is important for you to avoid W3C validation errors. Is this because of some formal requirements, or you are having some technical difficulties?

Regards,
Dmitry
Click to view Dmitry Pikhulya's profile TeamDev Ltd. 147 posts since
Jan 5, 2007
3. Jul 30, 2008 6:59 PM in response to: Oliver Nelson
Re: W3C validation problem: <nobr> in DataTable component
Oliver,

We didn't consider working on the full W3C conformance in the near future because some current limitations of JSF 1.x make it very hard or even impossible in some cases. For example a component cannot place additional content into the <head> tag, and it's hard to reliably work around this while having features like Ajax and Portlets compatibility. Though there are the cases when W3C conformance issues can be easily fixed, like the two cases that you have pointed out. We currently cannot focus on finding and resolving these issues ourselves, so please let us know if there are any more issues that you would like to see resolved.

Regards,
Dmitry