Closed ArdentZeal closed 9 years ago
That wasn't introduced in 2.3.0; it's been around since forever, I guess. But the tab key is only processed when the autocomplete list is open. When it's closed, that keystroke is ignored and the browser should handle it normally.
That is true, but I am using load-on-focus and would like to keep doing so.
Kind Regards
Sent from my iPhone
On 02.04.2015, at 06:14, Michael Benford notifications@github.com wrote:
That wasn't introduced in 2.3.0; it's been around since forever, I guess. But the tab key is only processed when the autocomplete list is open. When it's closed, that keystroke is ignored and the browser should handle it normally.
— Reply to this email directly or view it on GitHub.
There's an old requested feature to enable custom hotkeys and I intended to work on it for the next release. So maybe it'll be easier to turn off the tab
keystroke.
In the meantime I suggest that you fork this repo and disable the tab processing yourself. All you have to do is change this line.
Can this issue be closed?
Closing due to inactivity (the issue can always be reopened if necessary).
Hope you get to this. It's very unintuitive having tab make a selection from the autocomplete list.
Hello,
with the new version, the tab key selects the selected entry in the autocomplete list. We use tab to navigate through a table / forms and when we tab into a tags-input field, we got a problem.
Can this be an option, so we can disbale the behaviour and use tab as intended? Or is this a new bug introduced and was never planned that way?
Kind Regards