The cursor/caret used to appear at the beginning of the focused autocomplete in FF and IE.
This caused annoyances for users of those browsers who typed slowly since the page would
reload and when they startd typing again the text would appear before their last entries.
For example if someone was searching for 'john' but paused after 'joh', they would end up typing 'njoh', instead of 'john'. If they weren't paying attention, they might think there is no 'john', when they'd mistakenly searched for 'njoh'.
Coverage increased (+1.07%) to 39.09% when pulling 293e96854f28cb4ec3c68d0f984ca17ba6ef0fef on MerchantsBonding:put-cursor-after-existing-text-in-field into c36f2699309c872c7f52c27b6eac2169526bd1b5 on leikind:rails3.
The cursor/caret used to appear at the beginning of the focused autocomplete in FF and IE. This caused annoyances for users of those browsers who typed slowly since the page would reload and when they startd typing again the text would appear before their last entries.
For example if someone was searching for 'john' but paused after 'joh', they would end up typing 'njoh', instead of 'john'. If they weren't paying attention, they might think there is no 'john', when they'd mistakenly searched for 'njoh'.