Feedback & Nightly FixedColumns column aligning problem again
Feedback & Nightly FixedColumns column aligning problem again
Hi Allan,
some time ago you already helped me with a few issues I had with the FixedColumns plugin. (http://datatables.net/forums/discussion/9744/table-border-issues-w-and-wo-fixedcolumns#Item_11). I upgraded to the current nightly and wanted to give you some feedback. The solution with the scrollbar taking the whole table width is great! I have the feeling everything is working much smoother now. But I have issues with fixed column borders and column alignment again. I'm using your plugin in conjunction with twitter bootstrap and prepared a jsfiddle for you.
You'll notice the fixed columns header alignment isn't correct with the rows. This happens in every browser (tested on mac: chrome, firefox, windows7: IE9, chrome). It's just moved by one pixel most of the time.
Can you help again?
some time ago you already helped me with a few issues I had with the FixedColumns plugin. (http://datatables.net/forums/discussion/9744/table-border-issues-w-and-wo-fixedcolumns#Item_11). I upgraded to the current nightly and wanted to give you some feedback. The solution with the scrollbar taking the whole table width is great! I have the feeling everything is working much smoother now. But I have issues with fixed column borders and column alignment again. I'm using your plugin in conjunction with twitter bootstrap and prepared a jsfiddle for you.
You'll notice the fixed columns header alignment isn't correct with the rows. This happens in every browser (tested on mac: chrome, firefox, windows7: IE9, chrome). It's just moved by one pixel most of the time.
Can you help again?
This discussion has been closed.
Replies
Allan
http://jsfiddle.net/chmielot/csrja/
So the first thing I'd say is that sScrollX should always be 100% if it is used. It should not be used as a pixel value as odd things can happen (I will be updating the documentation to note this). If you want a smaller table, make the container element smaller.
Having said that, I'm actually not seeing the pixel offset myself. Indeed, the scrolling doesn't actually seem to be doing much in Firefox (nothing in fact) while its a little dodgy in Safari (container overlaps the bottom scrollbar - which it shouldn't I'll be looking into that).
Normally pixel offsetting is caused by `border-collpase:collapse` in the css, but it is set as separate here, so I'm afraid I'm not certain what is happening.
Allan
thanks for your answer. I am not sure why you can't see the pixel offset. Maybe I'll try to show you with the help of a screenshot: http://img837.imageshack.us/img837/3180/screenpixeloffsetfixedc.png
Don't you have this issue? I tested on Mac and Windows.
Kind regards,
Thomas
Allan
I have the same issue. The alignment of columns is off in the version 2.0.3 for table with a complex structure (it's much better output than the nighty, though). And the Chrome seems to work the worst.
Link for
http://live.datatables.net/osaqow/7
Link for
http://live.datatables.net/osaqow/6
The html code could look unwieldy that is because it is auto-generated at runtime.
Artjom
When it comes to Chrome rendering then it seems that the height of some rows in the fixed columns is calculated incorrectly. Any thoughts? See http://live.datatables.net/osaqow/7
Allan