I've reverted the uptime column behaviour. I've spent the past 9 hours finding, testing and iterating a "better" way.

Hopefully this keeps everyone happy.
Update to the next main release and do a hard refresh.

9 hours ago, chodeus said:

I suspect you’re having a cache issue regarding the logic change so you might need to do a couple of hard refreshes in a row to sort it out.

From the way you wrote and explained it, I believe I'm seeing exactly the new, intended behavior that you are describing. It's not behaving any differently, even after a hard refresh or inside a private window - so I doubt this is a caching issue.

I'm merely stating that this new behavior has unintended and, at least for me, highly undesirable consequences.

9 hours ago, chodeus said:

Also “at a glance” uptime doesn’t appear for containers in folders. This behaviour hasn’t changed.

I know, but your immediate use assumption is already wrong: Not all of my containers are organized in folders!

The primary and most important as well as any in progress of being configured and deployed ones are not, and I want to be able to immediately see their uptime and/or exit code when I load the docker page. This change no longer allows for that and requires horizontal scrolling to access it before even opening any folders. Seriously, trying to configure and deploying new and complex containers is made needlessly harder by this plugin now doing everything it can to constantly hide the exit code.

The "jitter" I'm complaining about is the fact that the "Uptime" column and its content is visible during page load only to then jump outside the viewframe once the page has finished loading.

I'm using the Docker view in "Advanced Mode" and FolderView3 in its "Classic" style defaults.

Making vital information like Uptime and Exit Code only accessible via horizontal scrolling and making it impossible to see both the container name and its uptime at the same time on a 32" wide screen is an absolutely abysmal user experience.

I understand what you are trying to solve with this, I really do. And you clearly value the information you are now hiding less than others. But you unintentionally created far more harm with this change than good, at least for my workflow. If this behavior remains the way it is, I can only revert to the previous build or fork my own private "FolderView4".

1 minute ago, chodeus said:

Hopefully this keeps everyone happy.

Looks like we clicked "Submit" at the exact same moment. I guess I didn't need to write that fiery speech against this new behavior after all.

Anyway, thank you so very much for listening - even anticipating. Can't wait for the next build.

It certainly will make me very, very happy again.

EDIT: I just upgraded to 2026.06.23 and all is well again. I'm seeing extremely little shifting when opening and closing folders, a pixel or two at most. Maybe all it takes for this to work smoothly is to have at least a single container not organized in a folder?

Edited June 23Jun 23 by csb

1 minute ago, csb said:

Looks like we clicked "Submit" at the exact same moment. I guess I didn't need to write that fiery speech against this new behavior after all.

Anyway, thank you so very much for listening - even anticipating. Can't wait for the next build.

Fiery speeches are never required when you're using plugins that people volunteer their free time to maintain.

I started maintaining FolderView3 for my own benefit and when I decided to share this with all the FolderView2 users I agreed to take advice/recommendations/suggestions from the users but I did not agree to receive fiery speeches.

Unfortunately, sometimes the only way to receive feedback is to push changes because most people only come here when they have issues.

Update, and if there's issues please provide me with constructive feedback, screenshots and a debugging .json and I'll do the best I can to keep you and everyone else happy 🙂

Cheers!

Edited June 23Jun 23 by chodeus

I hope you can see that, while passionately making my point for the old and against the changed behavior, at no point did I resort to personal attacks or even demanded anything from you. I believe my feedback was sufficiently descriptive and constructive. Likewise, I truly value your time and contribution and at no point wanted to diminish that.

In fact, I'm now genuinely trying to understand what you even tried to fix with it because I'm simply not seeing the "jitter" you were trying to address. Maybe you could tell me how to reproduce it? There may be better ways to address it.

Just now, csb said:

I hope you can see that, while passionately making my point for the old and against the changed behavior, at no point did I resort to personal attacks or even demanded anything from you. I believe my feedback was sufficiently descriptive and constructive. Likewise, I truly value your time and contribution and at no point wanted to diminish that.

In fact, I'm now genuinely trying to understand what you even tried to fix with it because I'm simply not seeing the "jitter" you were trying to address. Maybe you could tell me how to reproduce it? There may be better ways to address it.

It's only evident for those with all containers in folders.

It's only slight but that's the level of OCD I'm working with. I spend a hell of a lot of time iterating changes to try and get it to appear just right.

When you expand a folder, to make room for the Uptime Column, the preview row jumps to the left very slightly. This is the jitter I was trying to fix and had fixed by having the Uptime Column push right instead of left when it appears. But unfortunately this is the behaviour you disagreed with and I understand why.

I think what I've achieved today is the best it'll get until the new webUI comes in. Hopefully I havent created new edge cases!

Yeah, I just put all my "loose" containers into a Test-Fold and I see what the problem is. It zeros out and hides the - then empty - Uptime column. Makes sense.

It's not really a lot of jitter, but it shifts a little when opening Folders, and it isn't exactly super smooth. It still beats the usability-monster that is horizontal scrolling by miles, though.

11 minutes ago, chodeus said:

I think what I've achieved today is the best it'll get until the new webUI comes in.

I agree. I don't see anything really wrong with the current implementation other than it being about as rough around the edges as the entire rest of the Unraid interface - feels very native. 😅