I'm trying to upgrade our UltraWebGrid to the new WebDataGrid and I'm having trouble with the css. I want the grid to show 1px borders, even if there is no data in the cell. Our old grid looks like this:
And the new grid looks something like this:
The places where data is missing don't apply the css, so the grid has a bunch of empty sections with no grid lines. Here is the css I'm using to apply the borders:
tbody.igg_BorderClass>tr>td{border: 1px solid #BBB;}
This is set under the ItemCssClass property of WebDataGrid. Any help is appreciated.
Thanks,
Mike
Hello Michael,
Thank you for contacting Infragistics!
We received your support request concerning borders and css styles of the WebDataGrid and empty cells, and this case has been assigned to me. Infragistics is dedicated to helping you solve this issue. Our team and I have done an initial review of your case and I am looking into this matter and will get back to you by the end of the day Friday with more information or questions for you.
Sincerely,Mike P.Developer Support EngineerInfragistics, Inc.www.infragistics.com
Hi Mike,
Thanks for the quick response.
I was actually able to solve this issue by switch from the default style to a (slightly) modified version of Claymation, which looks very similar to the old grid. However, I do have 2 new issues, if they can be answered here:
1. I want my grid to not allow wrapping of text onto a new line. The rows should have a fixed height of 15px and cut off any extra data that doesn't fit in the cell. I've achieved this for the most part by adding "white-space:nowrap" to the tbody.igg_ClaymationItem>tr>td tag in the css. However, it doesn't work on the first row, only every row that follows.
2. In IE8 (which is where this grid will be used almost exclusively) there seems to be an issue with selecting cells. When I try to click a cell, it always selects the cell 2 rows to the left. I tested the same page in Chrome and it works fine, but I need it to work in IE8 as well.
Thanks again,
Thanks again for the prompt response. I was actually (again) able to solve both issues. Our old pages used the following line to emulate IE7:
<META http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
Removing this line fixed both issues.
Hello Mike,
Thank you for the update. I have done some looking into this matter and have created a sample. I have been unable to reproduce either of these issues. I am attaching my sample demonstrating this. To make this sample I used 12.1.20121.2072 of NetAdvantage for ASP.NET 2012 Volume 1. Do you have an isolated sample that reproduces this issue you can provide me? What version of NetAdvantage are you using? What is the version of IE8 you see this issue in?