It's 100% unrealistic to expect to run something like TableSorter on the client side for 10,000 rows of data
what user is really going to see/use that much data at once? look into paging the data and make the UI more usable On Jan 15, 8:20 am, dyutiman <dyutiman.chaudh...@gmail.com> wrote: > Hi, > If my table contains near about 10000 rows, because of tablesorter > plugging the page is getting hanged in Firefox2. I didn't check in > other browser as it must be fixed in FF first. > And I have no idea how to debug or solve the problem. Anybody faced > the problem before?
