Details
-
Bug
-
Resolution: Fixed
-
Low
-
2.6.0
-
None
-
None
Description
caching was being done in our javascript autocomplete library is based on results rather than queries. So if you search for nothing (eg. clicked the drop down), the first 50 results would display. if any one of those matched your next query, it would not go back to the server, and in fact use a less restrictive regex than the server - a word boundary is not required before the search term.
fix: disable client side caching