- This topic has 1 reply, 2 voices, and was last updated 8 years, 6 months ago by
.
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
These forums are now closed and remain for historical purposes.
None of the content applies to the new version 3. For support, get in touch via our contact form.
Trevor.
Whenever trying to type into a search field the refreshing of option counts for the other facets pulls focus from the search box and interrupts data entry into the search field. This sets the cursor back to the start of the search field.
Unless data is entered into the search field fast enough ( i.e. before the recalculation of option recount ) it produces typos in the search field.
An example is when trying to type in “rubber” the cursor reset causes “berrub”
http://mashcast.net/shop-by-keyword/
Paul
This will be because the plugin has a timer that waits after a keystroke for the user to type a word, and that setting is too fast for your use. One thing you can try is to disable the Update the Search Form on user interaction and see if that helps, or is the form actually submitting?
This sensitivity setting is currently fix, but I am hoping that V3 of our plugin will make this an option you can set.
Also, after a form has reset, the cursor goes back to the start of the text. This is annoying but it is a browser/HTML standard. There are many threads about this on stackexchange, such as this:
You might use javascript to attach an event like this to the text field.