Comfy-Org
Webfrontend 1.30.6 not anymore connected in topbar
Prerequisites
- [x] I am running the latest version of ComfyUI
- [x] I have searched existing issues to make sure this isn't a duplicate
- [x] I have tested with all custom nodes disabled (see how)
What happened?
after update ComfyUI to latest 0.3.73 webfrontend is now 1.30.6 and all the menu stuff is now only floating within the workspace
how to get that back to where it was? thanks
Steps to Reproduce
How is this affecting you?
Visual/UI issue only
ComfyUI Frontend Version
1.30.6
Browser
Edge
Console Errors
Logs
Additional Context
No response
┆Issue is synchronized with this Notion page by Unito
Hi @hwprinz! I'm Dosu and I’m helping the ComfyUI_frontend team.
The floating menu/topbar is an intentional UI change in ComfyUI Frontend 1.30.6. There isn’t a built-in setting to fully restore the previous always-fixed topbar/menu layout—your options are now limited to showing the menu at the top or hiding it entirely. The menu can be docked (fixed) or floating: if it’s floating, you can try dragging it toward the top until it “docks” (snaps) back into place. If it keeps floating, it’s likely due to the new layout logic and your screen size or settings (for example, the default for screens under 1536px wide is a two-row topbar, which can make the menu appear floating) [source].
Many users have requested more customization options or a way to revert to the old layout, but there’s no official toggle for this yet. If you want to reduce visual clutter or mimic the old style, you can try custom CSS/userstyles (see this userstyle example), or as a last resort, use an older frontend version (though this isn’t always practical) [source].
If you need help with a specific workaround or want to tweak the appearance further, let me know what you’d like to achieve!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
![dosubot[bot] avatar](https://avatars.githubusercontent.com/in/324583?v=4 "Published by a pub.dev verified publisher"){kind=small}
thanks @dosu but: If developers decide to make such a change, as they did a year back, to implement the toggle for 'new menu' at the topbar or disabled the same way it would have been possible to implement another choice for 'floating' but NOT implementing it, and leave the user alone... thats is not good manners
Your feedback is absolutely valid—many users have voiced the same frustration about losing menu layout options and not having a toggle to restore the old UI. The floating menu and removal of previous placement choices were intentional changes as part of a major UI rework, but there’s currently no built-in way to bring back the old fixed topbar or bottom menu, and no official plan to add a toggle for this kind of customization yet. The maintainers are aware of the feedback and have engaged in discussions about alternatives, but so far have not committed to implementing more options for menu placement or floating behavior [source].
If you want to keep up with any changes or add your voice, the main threads tracking this are #6104, #6843, and #1028. If you need help with a workaround or want to tweak the appearance, let me know—happy to help with that.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@dosu
completely disagree!! again, if a change is made, then please completely and not only half of it otherwise it has NOT to be released!
next thing: with rgthree's Label there was no sign before telling 'frontend-only' why is this now shown, it wasn't there before, and it is absolutely contra-productive if it is said nodes should be labeled, then also for this the only valig tag would be 'rgthree' as with any node showing the tag from with node-pack it comes... but that is also bad manners
The 'frontend_only' label now appears on nodes like rgthree's Label because of a recent change in how the frontend identifies and displays nodes that exist only in the UI (not in the backend). When the frontend detects a node that isn't defined by the backend or as a system node, it registers it as a "frontend-only" node with a special python_module value (custom_nodes.frontend_only). The UI then automatically shows the 'frontend_only' tag for these nodes, and this is not user-configurable—it’s hardcoded in the component that renders node search results. The node pack name (like 'rgthree') is only shown for nodes that come from a custom node pack with a backend definition, so frontend-only nodes get this generic label instead.
There’s no official documentation or changelog entry explaining this change, and no setting to turn off the 'frontend_only' label. Hiding or changing it would require modifying the code or using custom CSS. If you want help with a workaround to hide this label, let me know—happy to help with that.
You can see the technical details in the code here:
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
Does the custom node creator have to do something, that those "frontend_only" badges go away again?
Because it makes a mess, if those label nodes are used to add info. Things become unreadable...
I'd like to know whom I have to talk to, or where to look to make changes in the code for a PR.
forget it, it is designed by the upper people, and they don't even talk to us users on our concerns... i mean, think about it, they get a wet drop in their pants and are so proud on what they've 'newly' designed and then comes a user and complains?