Autocomplete/autosuggestions are not language-context sensitive

I am still experiencing this when using the autocomplete form element in a custom form. I saw the patch in #13 🐛 Autocomplete/autosuggestions are not language-context sensitive Fixed so I was re-rolling this so it works with the latest version.

Ignore the two patches above, here we go 😇

Ignore the patches above, here we go 😇

I have the same issue as @yannickoo

Patch #43 seems to work correctly.

🐛 Autocomplete/autosuggestions are not language-context sensitive with custom form Needs review

Hello,

previous patches do not apply on the 1.9 version .
Here is a patch to use language filter on autocomplete suggestions.

Re: exposed filters.

There is a way to get submitted Views exposed filter values passed to the autocomplete query as additional data. Here is a patch that makes the search query aware of submitted exposed input values.

Note 1: This still can't pick up live changes to the exposed filter form as @drunken monkey explained in #11 and #27. In simple cases, it may be possible to autosubmit the form when a trigger element is changed, which would rebuild the submitted input data, but this may not be a good solution for every form.

Note 2: If you are using one of the above patches that sets the query language to the current site language, then the site language cannot be overridden by an exposed language filter using this patch (the site language takes precedent), but other exposed filters should work.