-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabling liveSearch does not work #1152
Comments
Seems like the issue is in .bind( 'search change keypress '.split( ' ' ).join( namespace + ' ' ), function( event ) where this condition
has been changed to this if ( wo.filter_initialized && ( event.which === tskeyCodes.enter || event.type === 'search' ||
// only "input" event fires in MS Edge when clicking the "x" to clear the search
( event.type === 'change' || event.type === 'input' ) && this.value !== c.lastSearch[column] ) ) { When removing the added condition event.type === 'input' the disabling of liveSearch works. Or replacing it with ( event.type === 'change' || (event.type === 'input' && wo.filter_liveSearch === true)) I am not sure why the |
Hi @kelesi! I'm looking into this now. Thanks for reporting the issue and doing some troubleshooting! |
Ok, I have a fix available in the master branch... I was trying to write a unit test, but sadly I've run out of time for messing around this morning 😉 |
Version 2.25.4 is now available with this fix! |
Hi @Mottie, |
Hi @kelesi! Sorry for the delay in responding, I've just returned from a much needed extended vacation. It appears that the liveSearch setting was bypassed when an "input" event listener was included to fix issue #1280. I'll need to figure out the best way to deal with this new issue... either ignore the "input" event when the |
Setting the |
I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue the discussion in this thread. |
In v2.25.3 setting "filter_liveSearch : false" does not disable liveSearch. It was working in v2.23.5.
The text was updated successfully, but these errors were encountered: