Multiple onColumnSearch events when user has not touched the filter field

[hepcat72]

Description

I have an issue that seems related to #1605. The onColumnSearch fires an event on page load. To work around it, I used a "loading" variable that I update after a timeout to prevent the repeated page load. Why do I have to do this and how can I make this work-around unnecessary?

Example(s)

        document.addEventListener("DOMContentLoaded", function(){
            var loading = true;

            $('#file_list').bootstrapTable({
                onColumnSearch: function (columnName, searchTerm) {
                    if (!loading) {
                        // NOTE: I will have to populate the column searches on page load
                        // NOTE: Turns out that one page load, a column search event is triggered, so we check to see if anything changed before triggering a page update.
                        let oldTerm = getCookie('archive-file-filter-' + columnName);
                        let oldTermDefined = typeof oldTerm === "undefined" || !oldTerm;
                        let newTermDefined = typeof searchTerm === "undefined" || !searchTerm;
                        if (oldTermDefined !== newTermDefined || (oldTermDefined && newTermDefined && oldTerm !== searchTerm)) {
                            setCookie('filter-' + columnName, searchTerm);
                            console.log("COLUMN SEARCH EVENT:", columnName, searchTerm);
                            updatePage();
                        }
                    }
                },
            });

            setTimeout(function () {loading = false}, 2000);
        });

As you can see, I already suppressed multiple repeated loads by checking the search term against the previous search term.

I'm in the middle of developing this page and I have not yet set the searched term on page load, so could this be that BST is keeping track and sees the empty field and assumes it's a new search, thus triggering the reload?