De-selecting a search category is sometimes ignored. [bug] [low priority]

[LilithHafner]

When de-selecting a search category and immediately resuming typing (within 300ms), the de-selection is not registered. This is due to the use of a a single debounce timer shared between get_filters and update_search which allows a debounced get_filter call and a subsequent debounced update_search call get handled by a single update_search call which notably fails to update filters in this case.

Documenter.jl/assets/html/js/search.js

Lines 166 to 191 in f85c471

	$(document).on("keyup", ".documenter-search-input", function (event) {
	// Adding a debounce to prevent disruptions from super-speed typing!
	debounce(() => update_search(filter_results), 300);
	});
	$(document).on("click", ".search-filter", function () {
	if ($(this).hasClass("search-filter-selected")) {
	$(this).removeClass("search-filter-selected");
	} else {
	$(this).addClass("search-filter-selected");
	}
	// Adding a debounce to prevent disruptions from crazy clicking!
	debounce(() => get_filters(), 300);
	});
	/**
	* A debounce function, takes a function and an optional timeout in milliseconds
	*
	* @function callback
	* @param {number} timeout
	*/
	function debounce(callback, timeout = 300) {
	clearTimeout(timer);
	timer = setTimeout(callback, timeout);
	}

#2407 should make the required interaction speed 100ms instead of 300ms which should make this issue nearly impossible to reproduce for folks not using automated GUI interaction.

Implementing #2410, however, would streamline the GUI to the point where even at 100ms it would be plausible to run into this bug accidentally.