DominikDoom/a1111-sd-webui-tagcomplete

Fork 0

mirror of https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git synced 2026-11-05 00:17:25 +00:00

[GH-ISSUE #323] Style seems wrong on sd-webui-forge-classic #224

New issue

Closed

opened 2026-10-30 21:21:15 +00:00 by bsakaguchi · 8 comments

bsakaguchi commented

2026-10-30 21:21:15 +00:00

Owner

Originally created by @equal-l2 on GitHub (Apr 15, 2025).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/323

Candidates should be in a floating element, but it renders inline instead.
EDIT: It works fine with stable-diffusion-webui-forge.
Browser: Firefox 137 (Edge has the same problem)
OS: Windows 11
Python: Python 3.11.11

I'm using sd-webui-forge-classic at 0dc0d17.

Thank you for your amazing extension by the way!

Originally created by @equal-l2 on GitHub (Apr 15, 2025). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/323 Candidates should be in a floating element, but it renders inline instead. EDIT: It works fine with stable-diffusion-webui-forge. Browser: Firefox 137 (Edge has the same problem) OS: Windows 11 Python: Python 3.11.11 I'm using sd-webui-forge-classic at [`0dc0d17`](https://github.com/Haoming02/sd-webui-forge-classic/commit/0dc0d17cf9cfd4f2ff345f00bb4c222b558e00b1). ![Image](https://github.com/user-attachments/assets/15d123f3-499c-4b4a-a337-febf7d691fbb) Thank you for your amazing extension by the way!

bsakaguchi closed this issue

2026-10-30 21:21:15 +00:00

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 15, 2025):

The styling for the popup is mostly applied by the code at runtime, so if it looks wrong, that usually actually means the script had some other error causing it to get interrupted. Could you open the browser console (CTRL+SHIFT+I) and tell me if there are any error related to tag autocomplete there?

@DominikDoom commented on GitHub (Apr 15, 2025): The styling for the popup is mostly applied by the code at runtime, so if it looks wrong, that usually actually means the script had some other error causing it to get interrupted. Could you open the browser console (`CTRL+SHIFT+I`) and tell me if there are any error related to tag autocomplete there?

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@equal-l2 commented on GitHub (Apr 15, 2025):

This log is the only one that seems relevant:

Uncaught (in promise) DOMException: Node.appendChild: Cannot have more than one Element child of a Document
    setup http://127.0.0.1:7860/file=extensions/a1111-sd-webui-tagcomplete/javascript/tagAutocomplete.js?1744729216.1708498:1603
    async* http://127.0.0.1:7860/file=extensions/a1111-sd-webui-tagcomplete/javascript/tagAutocomplete.js?1744729216.1708498:1619
    executeCallbacks http://127.0.0.1:7860/file=script.js?1744727145.8427105:66
    mutationObserver http://127.0.0.1:7860/file=script.js?1744727145.8427105:95
    MutationCallback* http://127.0.0.1:7860/file=script.js?1744727145.8427105:89
    EventListener.handleEvent* http://127.0.0.1:7860/file=script.js?1744727145.8427105:88
tagAutocomplete.js:1603

@equal-l2 commented on GitHub (Apr 15, 2025): This log is the only one that seems relevant: ``` Uncaught (in promise) DOMException: Node.appendChild: Cannot have more than one Element child of a Document setup http://127.0.0.1:7860/file=extensions/a1111-sd-webui-tagcomplete/javascript/tagAutocomplete.js?1744729216.1708498:1603 async* http://127.0.0.1:7860/file=extensions/a1111-sd-webui-tagcomplete/javascript/tagAutocomplete.js?1744729216.1708498:1619 executeCallbacks http://127.0.0.1:7860/file=script.js?1744727145.8427105:66 mutationObserver http://127.0.0.1:7860/file=script.js?1744727145.8427105:95 MutationCallback* http://127.0.0.1:7860/file=script.js?1744727145.8427105:89 EventListener.handleEvent* http://127.0.0.1:7860/file=script.js?1744727145.8427105:88 tagAutocomplete.js:1603 ```

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 15, 2025):

Thanks for the log. I just tried it on a fresh installation of forge classic, same commit as yours and everything seems fine. So I suspect it is caused by a settings issue or a conflict with another extension. Did you copy-paste anything from another or older webui / forge installation?

Edit: This could for example also be caused by two copies of tag autocomplete being installed at the same time in differently named folders

@DominikDoom commented on GitHub (Apr 15, 2025): Thanks for the log. I just tried it on a fresh installation of forge classic, same commit as yours and everything seems fine. So I suspect it is caused by a settings issue or a conflict with another extension. Did you copy-paste anything from another or older webui / forge installation? Edit: This could for example also be caused by two copies of tag autocomplete being installed at the same time in differently named folders

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@equal-l2 commented on GitHub (Apr 15, 2025):

I believe I have a fresh install of forge-classic, but I'll try reinstalling tomorrow.

P.S.: I didn't mention I'm using Windows, which may be a clue. Edited the main post.

@equal-l2 commented on GitHub (Apr 15, 2025): I believe I have a fresh install of forge-classic, but I'll try reinstalling tomorrow. P.S.: I didn't mention I'm using Windows, which may be a clue. Edited the main post.

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 15, 2025):

I'm also on Windows, so I don't think that is related. The error from the log is specifically about the style node being unable to be added.

I only know of this happening if
a) another extension added something there first which gets in the way
b) two versions of tagcomplete are competing against each other
c) the webui wasn't properly restarted after installing the extension

To be safe you could also try restarting forge classic and force-refreshing the webpage with CTRL+F5 in case something outdated was loaded from the browser cache

@DominikDoom commented on GitHub (Apr 15, 2025): I'm also on Windows, so I don't think that is related. The error from the log is specifically about the style node being unable to be added. I only know of this happening if a) another extension added something there first which gets in the way b) two versions of tagcomplete are competing against each other c) the webui wasn't properly restarted after installing the extension To be safe you could also try restarting forge classic and force-refreshing the webpage with `CTRL+F5` in case something outdated was loaded from the browser cache

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@Terroosh commented on GitHub (Apr 15, 2025):

Having https://github.com/zanllp/sd-webui-infinite-image-browsing enabled is causing it, which really sucks.
It only happens on Forge Classic too. The two extensions work just fine on reForge.

@Terroosh commented on GitHub (Apr 15, 2025): Having https://github.com/zanllp/sd-webui-infinite-image-browsing enabled is causing it, which really sucks. It only happens on Forge Classic too. The two extensions work just fine on reForge.

bsakaguchi commented

2026-10-30 21:21:16 +00:00

Author

Owner

@DominikDoom commented on GitHub (Apr 16, 2025):

@Terroosh Thanks for tracking it down, though this conflict probably isn't unique to infinite-image-browsing.
The reason it was broken only on forge classic is that the gradioApp() function returns a different root node there compared to standard webui / reForged. I add the style to a better spot now, so it shouldn't conflict in the future.

@DominikDoom commented on GitHub (Apr 16, 2025): @Terroosh Thanks for tracking it down, though this conflict probably isn't unique to infinite-image-browsing. The reason it was broken only on forge classic is that the `gradioApp()` function returns a different root node there compared to standard webui / reForged. I add the style to a better spot now, so it shouldn't conflict in the future.

bsakaguchi commented

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

Author

Owner

@equal-l2 commented on GitHub (Apr 16, 2025):

Thank you for the fix, it works perfectly!
(I should have mentioned about infinite-image-browsing, sorry)

@equal-l2 commented on GitHub (Apr 16, 2025): Thank you for the fix, it works perfectly! (I should have mentioned about infinite-image-browsing, sorry)