This question is locked. New answers and comments are not allowed.
There seems to be a difference in how the cells are generated when using server binding vs client ajax binding.
In server binding if the column is blank, the cell is rendered as <td> </td>.
In Ajax client binding if the column is blank, the cell is rendered as <td/>.
Normally the schematic difference would not be concerning, however in IE8, it causes differences in how the borders are rendered...
In server binding, the left border is present, in AJAX client binding the border-collapse: separate causes the left border to disappear.
Is there a way to force the Ajax client binding to render the cell as <td> </td> so the borders display properly in IE8?
-Tim
In server binding if the column is blank, the cell is rendered as <td> </td>.
In Ajax client binding if the column is blank, the cell is rendered as <td/>.
Normally the schematic difference would not be concerning, however in IE8, it causes differences in how the borders are rendered...
In server binding, the left border is present, in AJAX client binding the border-collapse: separate causes the left border to disappear.
Is there a way to force the Ajax client binding to render the cell as <td> </td> so the borders display properly in IE8?
-Tim
