You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a wish: would it be worthwhile to add the ability to show ajax processing? For example, I have extra code that reduces the opacity of the table rows whenever ajax is processing rows due to filterStart, sortStart or pageMoved:
$('table tr td').css('opacity',0.25);
Upon ajaxComplete, then the opacity is set back to 1. Such formatting could be hardcoded to occur if the appropriate option is select or somehow give admins the ability to customize the formatting effect desired.
The text was updated successfully, but these errors were encountered:
As it stands right now, a tablesorter-processing class name is added to the headers when the showProcessing option is set to true. This is actually set up to occur 500 ms after the start of the process to prevent the processing icon flashing on the screen. It's probably a moot point for sorting though since javascript is single threaded and 500 milliseconds in, it'll be chugging away and ignoring anything else; but it should work fine for asynchronous processes.
Also, If only one header is being targeted (sorting or filtering), then only that header will show an indicator. And that can be modified by css (here is the blue theme specific code).
I guess I could also add a class name to the table so you can apply whatever other styling you desire.
This is a wish: would it be worthwhile to add the ability to show ajax processing? For example, I have extra code that reduces the opacity of the table rows whenever ajax is processing rows due to
filterStart
,sortStart
orpageMoved
:Upon
ajaxComplete
, then the opacity is set back to 1. Such formatting could be hardcoded to occur if the appropriate option is select or somehow give admins the ability to customize the formatting effect desired.The text was updated successfully, but these errors were encountered: