Skip to content

Commit f28aee1

Browse files
Update README.md
I removed Adetailer 1st, 2nd, 3rd, etc. Tabs buttons from what wouldn't work. I found that they don't need to be selected and have their own UI element names named after each tab number. I plan to work more on this soon, been super busy as of late. I also want to make a quick tutorial on how people can add extensions to be compatible with this if you don't want to wait for me to add it, but would be highly recommended to use brave browser, possibly firefox, and if on chrome you need Ublock origin to click block element, but not actually block it, but use it to get the ui element's name when editing the extension's script)
1 parent 7e3f791 commit f28aee1

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

README.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,11 +13,6 @@ Ok so when I add the settings to be carried over to this extension they have a n
1313
New Forge UI for Checkpoint selection has the same thing "component-1370", but reForge & old forge have something like this instead "setting_sd_model_checkpoint".
1414

1515

16-
Now Adetailer has the same issue when you inspect the 1st, 2nd, 3rd, etc, etc. tab selection buttons.
17-
![image](https://github.com/user-attachments/assets/4b26211b-b337-41f8-a43a-bb2656d38cb5)
18-
19-
20-
2116
Meaning, if everyone's UI autogenerates the id/name on those types of ui elements and it differs from each person's ui, it could indicate an internal gradio system that I do not know how to change.
2217

2318

0 commit comments

Comments
 (0)