Feedback on the floating menus

[dchatel]

Basically, I find it disturbing.

ComfyUI is an app that already deals with nodes represented as boxes that you move around and connect. If the menu becomes floating and/or disconnected like this, it creates more boxes, and now you need to pay some additional attention to discriminate if the box you're looking at is part of the menu or a node.

Sure, it's pretty, but it makes the experience more confusing for me.

I also do not like the login button. I know you have this API stuff going on, but I do not want to use that, and I do not want to be reminded that this option exists. You can have it in the options as usual, but at least give us an option to hide the button.

┆Issue is synchronized with this Notion page by Unito

[EasyComfyui]

it pretty bad and i had to go back to the old version

[dchatel]

I also just realized something when loading a particular workflow that I had set up such that its main interface use all the available space.

After floating menus, the main interface is obscured by the menus (even panning the workflow down to compensate for the new origin of the canvas). This shows that, contrary to what they claimed in the commit, this new interface does not increase available space, but decrease it instead. This is due to the extra padding/margin around the menus. Here a small screenshot when I shaded red a useless part of the new floating menu:

[CCpt5]

Yea, not big on this change. Would take time to get used to.

I mean, what about saving the queue in the event of a crash.....might be better use of time.

[JorgeR81]

This shows that, contrary to what they claimed in the commit, this new interface does not increase available space, but decrease it instead.

This is due to the extra padding/margin around the menus

I wish we had options for smaller padding.

---

Maybe even an option to have no gap between the floating panels.

[CoreyCorza]

And the menus still obstruct nodes so what is even the point Theres just mass amound of dead space that you can't interact with nodes

https://github.com/user-attachments/assets/3ccd095e-785f-48c2-9e2f-0f5ef210efb2

[CoreyCorza]

I gave this new change a fair chance but I'm also concluding that I'm not a fan of this change It just creates all these gaps between panels and makes the graph feel even more visually cluttered

I mean, it looks fine if you've got a template open with 4 nodes But in a serious workflow with lots of things going on - not good.

[JorgeR81]

And the menus still obstruct nodes so what is even the point

Yeah, they should at least give "semi-transparency" to the areas we can't interact with.

And once you do that, why not add an option for full opacity, so that we can have the Topbar back !

[dchatel]

Here's my idea:

The comfy/run/stop/clear buttons could be about 32 to 48px wide maximum, so a total of 128 to 192px. And the group could be movable and dockable on any border/corner of the screen. The myworkflow/mysubgraph area doesn't need to be large, just 1.5em max, so it contains the text and a very tiny padding. Custom nodes creators could use that tiny bar to add their own options if they want (like crystools resources monitor).

When opening the comfyui button (the leftmost button) you get the usual menu, but with the additional "login" option. To be clear, a login button has absolutely NO place anywhere on the main interface as a primary element. It should definitively be moved inside the comfyui menu, if you thought the login options inside the parameters were not enough. And if you really want to bother people with an obvious unmistakable login button, you can have it right in the middle of the screen when you start comfy : "login: yes/no".

When opening the workflow menu: You have the usual workflow options (save, save as, duplicate workflow, etc...) then you have a separation line and after that separation line you have a "opened workflows" dynamic menu similar to what you typically as "opened windows" in the window menu of other applications that can open multiple workspaces at once (eg. photoshop).

[Wprussell]

If we're taking a survey, Mark me down for..

"Startlingly bad".

Cruel_world

[scottmudge]

If they insist on keeping it this way, at least give us the option to disable all API-Node related features/UI elements. Most(?) people aren't ever going to use those, and the 'Login' button is super obtrusive and annoying.

[CoreyCorza]

Its hard to see where nodes end and ui starts now because everything is the same color/shape blending into each other and overlapping on each other, pretty bad design. Its all just visual clutter with no clear visual seperation of elements anymore.

[flynet]

I really don't like such updates, they move settings, every version to new locations. Please STOP doing this !

[JorgeR81]

There are also people using 2nd row tabs + bottom menu, that were affected by this.

• https://github.com/Comfy-Org/ComfyUI_frontend/issues/6125

---

Most people in this thread ( including me ), would like these changes to be reverted. But there is also people that don't like the way it was before ( when the double Topbar was introduced ).

• https://github.com/Comfy-Org/ComfyUI_frontend/issues/5095

---

I think the only change that would please everybody would be:

• Make all menus floating ( including workflow tabs ).

• Allow user to combine all floating menus ( like we can do now with the Queue menu )

• In combined menus, the drag area on the left side will control / move the whole panel.

• Allow users to drag all floating menus, to any canvas edge, and dock them there.

• Add options to create a full lenght bar, when a panel is docked to an edge.

This would also simplify other menu configurations. For instance, we don't need an option to have the Sidebar on the right. We just need to drag it to the right edge !

Comfy users like the freedom to recombine nodes as they wish. They would also like to do this for UI elements.

[ooofest]

OK, so it's not just me.

Among other things, I am so habituated to having all common functional needs lumped into the bottom of the window (above the feed section), but now with a portion at the top, I need to select some actions on the bottom, some on the top. You're wasting my time and splitting attention in this design, it's really not cohesive or efficient, IMHO.

And the floating widget/button to add a workflow "Run" to the queue seems missing, as well.

I've disabled the "new" menu and gone back to ye olde queue+options floating panel, but it's another problem because of its easy ability to blend into the workflow beneath it.

[Kashouryo]

For the annoying login button, put this into tampermonkey... make sure you edit the match to match your url:

// ==UserScript==
// @name         Comfy hide login button
// @description  Hide ComfyUI 1.30+ login button before an official way of hiding that button.
// @version      0.1
// @match        *://127.0.0.1:8188/*
// @grant        none
// ==/UserScript==

(function() {
    function hide() {
        document.querySelectorAll('button.p-button.p-component.p-button-secondary.p-button-outlined.text-neutral.border-black\\/50.px-4.capitalize.dark-theme\\:border-white\\/50.dark-theme\\:text-white').forEach(b => {
            b.style.display = 'none';
        });
    }
    hide();
    new MutationObserver(hide).observe(document.body, { childList: true, subtree: true });
})();

Your online API and such are really ambitious and I can very well imagine a future of customizable cloud powered generative AI workflows accessible to everyone, empowering people's imagination without expensive system limitation. But reminding me all the time for a feature I will not use? no.

[dchatel]

Any plans on giving the users an option to get rid of these floating menus ?

[christian-byrne]

Which ones in particular? What would an alternative look like?

[hwprinz]

@christian-byrne see also issue #6957

when the change was last year with the 'new menu' thing there was and is still the possibility to disable or have the new menu in topbar why is there now no option to set it floating, the way it is currently so sadly implemented..

pardon me to say, but just changing such and leave it to the user to deal with it, i almost microsoft behavior.

[dchatel]

Which ones in particular? What would an alternative look like?

A starting point would be to have an option to set either the menu as:

• legacy (which would correspond to the option "Disabled" in "Use new menu"
• Top (which would correspond to the option "Top" is "Use new menu" prior to the floating menus option in 1.30
• Floating (which would correspond to the current floating menus)

So basically, almost no change except for the option to revert the menus to what it looked like in version 1.28 : a fixed top bar and a fixed side bar.

BTW, the current implementation of the floating menus, when it comes to that side bar, is a bit clunky:

• if you open a menu, for example if you click on opened workflows, the side bar becomes connected, and the floating top bar moves away to the left, when we'd expect that the opened menu would actually be over the canvas, without moving anything.
• when no menu is opened, the side bar is "floating" but you cannot click on whatever is below the disconnected par of the side bar. Basically, it appears there is an invisible layer (a div or nav...) that consumes the hit test instead of letting the canvas eat it. Consequently, you can't click on anything on the canvas in that area, not you can drag the canvas from that area.

So in the current implementation, the "floating" aspect of the side bar is truly only aesthetic, and not functional.