FixedColumns + Complex Header + Serverside Processing = Unwanted Vertical Scrollbar

FixedColumns + Complex Header + Serverside Processing = Unwanted Vertical Scrollbar

JanuszJasinskiJanuszJasinski Posts: 36Questions: 0Answers: 0
edited June 2013 in Plug-ins
I'm using complex headers with fixedcolumns and server side processing. Works in Chrome and Firefox but in IE8 there is vertical scrolling in the non fixed columns on the right.

It looks as though the 2nd row that is kept in Chrome and Firefox is being used in IE to put the data (fixed columns) and as such it looks as though the rows in the fixed columns have been shifted up one row

Can anyone help? I am using [code]



$(document).ready(function () {
var oTable = $('#example').dataTable({
"bProcessing": true,
"sScrollX": "100%",
"bServerSide": true,
"sAjaxSource": "data.asp",
"sServerMethod": "POST",
"fnInitComplete": function () {
new FixedColumns(oTable, {
"iLeftColumns": 3
});
}
});

});
[/code] and [code]


Fixed1
Fixed2
Fixed3
Scroll1
Scroll2
Scroll3
Scroll4
Scroll5
Scroll6
Scroll7
Scroll8
Scroll9
Scroll10
Scroll11
Scroll12


AC
...





...



[/code]

Replies

  • JanuszJasinskiJanuszJasinski Posts: 36Questions: 0Answers: 0
    I've added a screenshot here: http://imgur.com/5BAAj5U.jpg
  • allanallan Posts: 63,498Questions: 1Answers: 10,470 Site admin
    Can you please link to a test case showing the problem: http://datatables.net/forums/discussion/12899/post-test-cases-when-asking-for-help-please-read

    Allan
  • JanuszJasinskiJanuszJasinski Posts: 36Questions: 0Answers: 0
    Ok this is bizarre. It works fine across all browsers when I uploaded it to test on my server (http://janusz.co.uk/dt/test.php) but when accessing it locally, it still has a major issue. For ease, the link provided uses just a static data file.

    Why would one server work and the other, not? Is IIS to blame somehow? A firewall? When run locally (on IIS), this is what I see in IE 8 - http://imgur.com/81Znxyc

    Thanks,

    JJ
  • JanuszJasinskiJanuszJasinski Posts: 36Questions: 0Answers: 0
    OK! It turns out it was to do with compatiability view in IE8!

    However this means that it doesn't work for IE7. Any ideas?
This discussion has been closed.