I have a grid implementation where the 1st column is too wide, but only in IE9. The specified column with is 45px, yet the actual column width is 144px.
here are some relavant grid initialization calls:
myself.grid.setInitWidths( “45,150,305,75” );
myself.grid.enableAutoWidth( true, 600, 100 );
The content of that column is a 16x16
icon. I have tried turning off auto width, but that did not fix the ‘too wide’ column.
I have another implementation of this grid that does not have this problem. it does not use auto width, and it has a variable column, yet making these changes to my grid did not fix the wide column either.
Any suggestions?
Unfortunately the issue cannot be reconstructed.
Try to update your dhtmlxGrid version.
If issue still occurs for you please provide a completed demo.
I have put up a demo of it at:
stone-ware.com/test/services.html
I have also found out that this issue only happens when IE 9 is using ‘IE 9’ browser mode and ‘IE 9 standards’ document mode. These are the default modes when i found this issue on my dev server.
However, on www.stone-ware.com, this page defaults to ‘IE9 Compat View’ browser mode and ‘IE 7 Standards’ doc mode. So, it will work for you when you view this site in IE9, unless you open up the dev toolbar and change your browser mode to IE9.
Since many of our customers access this page from the server that contains it (i.e. - loopback), this issue will affect them. I am not sure why the modes are different depending on the server, but there is probably some IE settings that is affecting this.
Anyways, I am not sure if you’d consider this a bug or not, so i’ll leave that up to you.
I figured out that the doc mode goes to ‘compat’ mode when the site is a local intranet site. Then, IE has an option to make local intranet sites use compatibility mode. The weird part is that IE 9 is not recoginizing 127.0.0.1 as a local intranet site, so i had to add 127.0.0.1 to my compatibility view site list for the issue to go away.
I still think our customer could experience this, but at least we have a workaround for them. Let me know, if you could, whether this is a known bug, has been fixed, etc.