lllyasviel / lllyasviel/stable-diffusion-webui-forge
Checkpoint dropdown in Gradio 4 - Too small, left-aligned and filter area is buggy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
When switching to the new version of forge, the checkpoint list has a couple of issues for me when I updated my Forge to the latest version. From this version:
To this version:
Problem 1 - Dropdown width
The dropdown is slightly smaller than it was before. I understand the reason, and it is fine, with a few caveats.
When the checkpoint dropdown is clicked, the new width is limiting the visibility of long paths. I know there's an option to ignore paths and just show the checkpoint names, but this is not a solution. The paths are there for a reason, to sort the checkpoints properly. I wish to see the paths, but also see the name of the file. With new Forge I cannot.
How it is now:
How it was before:
The key issue here is that it no longor shows the full width when the dropdown is clicked. I'm fine with the new shorter width when it's collapsed, for UI-purposes. But not at the cost of readability when clicking the menu.
Problem 2 - Text alignment
There has also been a change in the maximum width of the dropdown menu when it's expanded. This makes the list unreadable when you have long paths. I have extra folders added to the start due to how I have my checkpoint SSDs set up with symlinks and such.
How it is now:
As you can see, not seeing the filename is troublesome. Ideally this is not needed if we solve Problem 1, but if not, we should right-align this list to make it readable.
Problem 3 - Filter typing
When typing in the dropdown, it used to be that the text you write is shown in the entire dropdown view, this means that you can read what you type.
How it used to be:
How it is now:
But as it is right now, I only get the typing area overlapping with the down-arrow on the right side of the drop-down.
Thus I cannot see what I type and filter, making this extremely hard to use!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by locating the checkpoint dropdown implementation and reproducing the behavior with Gradio 4; done means expanded paths remain readable, alignment preserves filenames, and typed filter text is visible instead of overlapping the arrow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100