[GH-ISSUE #29] Request: Allows auto completion using the TAB #19

New issue

Closed

opened 2026-10-30 21:17:09 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-30 21:17:09 +00:00

Owner

Originally created by @uf-hy on GitHub (Oct 22, 2022).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/29

Originally assigned to: @DominikDoom on GitHub.

English is not my native language; please excuse typing errors.
When autocompleting tags , I can only seem to use the arrow keys and enter or click the candidate with the mouse, I feel this is not very easy to use.
It might work better if you could just press TAB to complete the first candidate as soon as one is available, and would also be in line with most ides

Originally created by @uf-hy on GitHub (Oct 22, 2022). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/29 Originally assigned to: @DominikDoom on GitHub. English is not my native language; please excuse typing errors. When autocompleting tags , I can only seem to use the arrow keys and enter or click the candidate with the mouse, I feel this is not very easy to use. It might work better if you could just press TAB to complete the first candidate as soon as one is available, and would also be in line with most ides

bsakaguchi

2026-10-30 21:17:09 +00:00

closed this issue
added the
enhancement
label

bsakaguchi commented

2026-10-30 21:17:11 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 22, 2022):

The reason I didn't do that at first is because tab changes the focused element in browsers, so I didn't want to interfere with navigation.
But with the current implementation, the autocomplete window blocks some navigation keys anyway as long as it's open, so I guess it isn't a big deal to allow tab to be used as well.

@DominikDoom commented on GitHub (Oct 22, 2022): The reason I didn't do that at first is because tab changes the focused element in browsers, so I didn't want to interfere with navigation. But with the current implementation, the autocomplete window blocks some navigation keys anyway as long as it's open, so I guess it isn't a big deal to allow tab to be used as well.

bsakaguchi commented

2026-10-30 21:17:11 +00:00

Author

Owner

@DominikDoom commented on GitHub (Oct 22, 2022):

If you selected one with the arrow keys, it will still choose that one on pressing tab, else automatically use the first one like you suggested.

@DominikDoom commented on GitHub (Oct 22, 2022): If you selected one with the arrow keys, it will still choose that one on pressing tab, else automatically use the first one like you suggested.