mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #233] Pops up with quality tag suggestions when not typing in text box #166
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
low priority
low priority
pull-request
question
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DominikDoom/a1111-sd-webui-tagcomplete#166
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Casuallynoted on GitHub (Sep 10, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/233
Ever since the 1.6 UI update, it's been pulling up 1-2 autocomplete boxes in the positive and negative prompts boxes, even when I'm not actively selecting them or typing anything. They'll stay there until I click in the box or click one of the prompts, and then quickly come back moments later.

Update: Seems to be it playing poorly with the tag auto format extension. This one prefers that the set of tags end in a comma, while auto format does not like that and removes the final comma.
@DominikDoom commented on GitHub (Sep 12, 2023):
Ah, that makes sense. The script listens to textbox input to show the popup, so it probably reacts to the auto formatter editing the content.
You can turn off the comma addition in the tag autocomplete settings, maybe that helps. By default it will always append comma and space to make writing long chains faster, but you can turn them off separately.
@DominikDoom commented on GitHub (Sep 12, 2023):
I think I was able to resolve it properly. Autocomplete will now ignore all input events that don't include an input type, which will only happen for events triggered from code like the formatter, but not for user input like adding, removing, copy-pasting etc.
The only manual exception being tag autocomplete's own update event, so it can react to the completion if needed, like for wildcards.
So for normal typing and editing the prompt there should be no difference, but the popup will no longer erroneously open after third party extension edits.