Spacing problems

[Joly0]

Unraid Version

7.2.4

FolderView3 Plugin Version

2026.04.17

What happened?

I have noticed, that the spacing of opened and closed folders is sometimes quite randomly and i am yet not sure what causes this, but here are a few screenshots which should show the problem. Whats also weird (which can be spotted on the last screenshot) is that another container is peeking below the first contaienr in the folder number 4 (which is also the problematic folder.

For the spacing it could be the "changelog" button that is added by the "docker versions" plugin, but i am not sure how this would create that "peeking" container when the folder is expanded.

Screenshots

2. 3. 4. 5.

Debug Log

[chodeus]

1. How many characters are the container names for your compose containers that cause the container name and status to wrap to a second line instead of being in line with the icon? (this is 1 issue). The container names must be quite long.
2. Have you tried removing the docker versions plugin, doing a hard refresh and seeing if you still get that container appearing/bleeding through? I am unable to repeat the issue where overflow containers appear when they are not meant to.
3. What other plugins are you running on your docker page? Github links would be great.
4. Any dev console errors present?

[chodeus]

Also for the container bleeding through, how many containers in that list have a changelog icon present?
docker.version adding a row to the update column is 1 issue and the length of your compose container names is the other issue.

Im just weighing up the fix and if it'll work considering you have other plugins making changes on the docker page.

If you wouldnt mind installing the beta update I have just done and see if that solves your container bleeding issue that would be great
https://raw.githubusercontent.com/chodeus/folder.view3/beta/folder.view3.plg

As for your long container names, native unraid doesnt truncate long container names and neither does FV3.

I'm wondering if this should be something for the compose manager plugin to deal with? Or alternatively I can provide custom CSS for you to try.

[chodeus]

If the above doesnt fix anything can you please send me your debug .json. On the forums is fine.

Go to your docker page, type "fv3debug" and reload the page. Make sure the .json downloads.
Then to turn it off just type "fv3debug" again and reload the page.

[chodeus]

You can try this in FolderView3 Settings > CSS > Customise > Variables (Docker) and then paste the below in the custom CSS box and click save. This will truncate any container names longer than 15characters. This is adjustable.

#docker_containers td.ct-name .appname a {
  display: inline-block;
  max-width: 15ch;
  overflow: hidden;
  text-overflow: ellipsis;
  white-space: nowrap;
  vertical-align: middle;
}

I think your issues are a combination of excessively long container names and the docker.version adding height to the update column.
I'd recommend against installing plugins that compete for room in the docker or VM tables that haven't factored in FolderView3 use.

[Joly0]

Ok, so there was a lot of input from you, so i will try to respond to everything.
First, so the custom css or the beta release doesnt solve the problem.
Uninstalling the docker.versions plugin does solve the bigger spacing problem that i posted with folder4, but as i have shown on my other screenshots (which however is really hard to see, is that there is still a spacing issue in general when various folders are expanded. For example when expanding the first folder, the "Network" column moves to the left slightly while the "container ip" column moves a bit more to the right, making more space between those two columns. But on the other hand when expanding the folder2 all columns left from "Autostart" move more to the left. I might have to make a video that should show this issue better, i think its not that easy to see from my screenshot. But problem is, the spacing problems kinda disappear (or becomes nearly unnoticeable when in incognito mode).
So regarding container name lenghts there are three containers in folder4 that have a longer name (longer than 20 characters), however folder1 also contains a container with a name longer than 20 characters, and that name is not cut of, but wrapped instead:
Folder1 Container:

Folder4 Containers: But i also niticed that when inspecting those containers,l there is a difference in html: Could be because one is a compose container and therefore doesnt have the onclick exec class added

Then other than the folderview3, the compose and the docker.versions plugin i am not running any additional plugins that shouldm interfere with the docker page.
And finally no, there are no errors or warnings or similar in the dev console.

[chodeus]

Sorry I'll try keep the essay's to the one comment and not think out loud as I try diagnose the issue.

So while trying to understand what you're experiencing I have noticed some other things and I'm not sure if it's related or not so I have released a new beta for you to see if that improves what you are seeing. I think part of your issue now is due to long container/network names pushing the table wider when you expand.
What I could see is the containers in the preview row jump around when you expand a folder. (This should greatly improve in todays beta)

Also sorry yeah I forgot to allow for compose containers with the custom CSS.
Also, I have included truncating long network names that may also be breaking your table and causing things to move a lot more.
If you want to test these in the custom CSS section of the plugin under "docker" and play around with the numbers in the max width this might help me diagnose what you're experiencing.

/* Truncate long container names (dockerMan, 3rd-party, and Compose) */
#docker_containers td.ct-name .appname a,
#docker_containers td.ct-name .appname {
    display: inline-block;
    max-width: 20ch;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
    vertical-align: middle;
}

/* Truncate long network names to prevent NETWORK column distortion */
#docker_containers tr:not(.folder) > td:nth-child(3) {
    max-width: 14ch;
    overflow: hidden;
    text-overflow: ellipsis;
    white-space: nowrap;
}

I appreciate your time getting back to me to help resolve this.

[Joly0]

Hey, sorry i forgot to answer you.
So after the recent update (i am now on 2026.04.22.1) the spacing problems and re-arranging of columns got way better. I have not tested the css you have given in your last reply.

The only thing i noticed now, but which i currently can not pin to what exactly is the reason, is the autostart column. I have a bunch of compose or 3rd party containers and the autostart column displays that for normal container without issues, so like this:

But when i open some folders, the column gets narrower and the text (or checkbox for normal containers) wraps to new lines:

1. Just wrapped text

2. Also wrapped checkboxes

I tried to figure out the values for the width of the different elements, but when i open the dev console, i get another weird bug that "solves" the initial issue why i even opened the dev console.
Before opening dev console with a bugged folder open:

After opening the dev console still with the bugged folder open:

I have no idea what causes this, but when i open the dev tools, the autostart column moves slightly to the left, which gives it more space and which unwraps all the fields in the column.

Btw, spacing and properly showing tables in css is a pita. Dont try to invest too much into this, its annoying maybe if you notice it, but it got way better with the last update. I just wanted to give an update and point out these edge cases.

[Joly0]

If i could, i would provide full screenshots, but the incognito button (as useful as it is, rly, i love that feature) also changes the length of the texts and therefore messes up the before and after completly, so its basically impossible for me to show this as full screenshot

[Joly0]

Ok, you can forget everything i just wrote. I just checked for updates of containers/plugins and saw there is the update to 2026.04.25.2 and so far everything i mentioned is fixed with this update

[chodeus]

Ok, you can forget everything i just wrote. I just checked for updates of containers/plugins and saw there is the update to 2026.04.25.2 and so far everything i mentioned is fixed with this update

If you wouldnt mind running the beta version for a little longer, I found a couple more edge cases that I'm working through as well as some firefox issues for someone else. Need to make sure I don't cause regression but I think I can get this a bit better before shipping to main.

[Joly0]

Sure, that's absolutely no problem. Just let me know when I should test something specific. I am also mostly using Firefox, so if there is also something I should look out for, just tell me :)

[chodeus]

If you're happy to update to beta release 2026.04.26.8 (latest beta) and make sure I haven't broken anything for you that would be great.
A lot of this was trying to improve CSS presets for Firefox users and also the visual bugs you previously described. I found some edge cases that I think I resolved yesterday but I'd love it if you tested to make sure it still looks okay with your docker page.

[Joly0]

Btw, i have tested with the latest beta release (i think it should now be 2026.04.30.1) and tested before with 2026.04.28 and so far i couldnt find any more problems regarding my specific issue or anything else that arised from the changes. The docker page for me looks clean and folder expansion doesnt mess up the whole layout anymore :)