JQuery + tablesorter + IE7 + large tables = hell

Question

I use the jQuery and tablesorter plugin, but with tables of significant size (900-1200 rows) the plugin just shreds Internet Explorer (7 and 8) stopped.

Yes, I would like to paginate (I can not); Yes, I want to tell everyone to use Chrome (I can’t), but I'm wondering if anyone has any other solutions. Perhaps a faster plugin to sort the table or something that I can try. I really don't want to do server side sorting.

Thanks!

Answer 1

How about page on page? Most likely, this is due to the DOM manipulation, and not with the sorting algorithm. Therefore, save the data in a javascript array, display only the first 20 elements and sort by array, not by elements.

Answer 2

I had exactly the same problem with exactly the same tools. The best you can do is try to make your HTML as clean as possible. And always remember to add the tfoot element before the tbody element. This will help IE make the table faster:

<table> <thead> <tr> <th>headers here</th> </tr> </thead> <tfoot> <tr> <td>footers here</td> </tr> </tfoot> <tbody> <tr> <td>body here</td> </tr> </tbody> </table> 

Even if you don't need a footer, do it like that. The only advice I have is to try some CSS tricks to either style or hide the table until javascript is loaded. Perhaps start with an animated gif download and delete it when javascript is executed.

Answer 3

IE 8 and Firefox do not seem to cope with large table dumps. They definitely croak for about 1000 lines. I saw this with my application.

Chrome is literally superfast and will load 1000 rows of HTML tables 100 times faster.

Chrome has one problem. After about 4,000 rows, the classes inside my cell tables fail. Mouseover associated with an action simply disappears and does not appear when the mouse is over a table cell.

While loading a 5000-line table is required 100 times, class links do not break in IE8 or Firefox. But who can afford to wait so long.

I think I opened a bug with Chrome and never heard back.

Since my webpage is running in a closed environment, it’s easy for me to get everyone to use Chrome.

In this case, the OPEN-SOURCE problem becomes a problem. No one can ask for help!