Change:
This feels similar to but that's marked as closed. I don't like the hamburger menu, I want to always see the normal menu bar. It already supports overflowing, but for some reason as soon as the Go menu overflows, it seems to be entirely replaced by the hamburger. I don't understand why this is (when there's already an overflow), and I would prefer it to just move more items into the overflow. The hamburger adds an extra click to get to the File menu (which is almost always the menu I'm using the mouse for). I've tried changing various settings, including setting "Menu Bar Visibility" to "Visible", but nothing seems to fix this (except disabling Command Center, but I feel like that shouldn't be necessary because a) there's an overflow for the menu and b) the command center appears to basically just be a mouse hit target, so could probably shrink in size?).
<!-- -96bd-47a8-a0e8- --This feature request is now a candidate for our backlog. The community has 60 days to the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our . Happy Coding!
is this not a bug? Why does the menu have an overflow, but not use it here? There is plenty of room for File/Edit/Selection/View but they all vanish and it's not clear to me why.
The goal of this change (we used to do what you are asking) was to try to bring some draggable real estate back to the crowded title bar.
aah, thanks for clarifying - although I'm not sure it's working that way. In my video above, there's no space to drag at the start of the video before I resize anything. Is there a reason there can't just be a small amount of padding for dragging, rather than snap from none to a huge amount? No matter what I do, VS Code always opens the window on my PC such that the menu bar appears then disappears and I have to resize it. It's one of the most frustrating things ever, because as soon as I've opened a new Window, I'm always going for File -Open. Yes, I should use the keybindings, but still.. The video didn't capture it, but I see the menubar appear, then quickly change to the hamburger
any strong feelings here? I believe you had originally suggested the minimum number of menus to be shown before collapsing to a hamburger
If this isn't to be changed, is there way to influence what "Window: New Window Dimensions: default" uses? I don't want any of the other options, I like these new windows being smaller and centered, they're just slightly too small so they trigger this.
No strong feelings. I believe some collapse-to-burger threshold should be kept but the actual value seems a bit aggressive right now
will try reducing the threshold next iteration
With the last upgrade this became worst for me. Now, aside of resizing, if my file has a long name, the menu collapses to a hamburger. To be honest, for me, it's preferable to have the menu over the file name because: I switch very often between recently opened files and projects, which are part of the File menu (so at least keep this one shown) The file name can already be seen in the tab, so I don't think this needs to have preference over the menu. As I don't use the new big search button (I prefer CTRL + P), I can drag the window by clicking in the window name or the vscode logo, so I always have enough space. Also, I think this is also a bug because: I have the settings set for the Menu Bar Visibility to be always visible, so Why does this get hidden? ! If I switch file to another with shorter name, the hamburger does not become a long menu again. My screens are not too big (1366x768 and 1024x768), so this is very noticeable.
LGTM, thanks!

Discussion:
// If below minimium menu threshold, show the overflow menu only as hamburger menu <del> if (this.numMenusShown - 1 <= showableMenus.length / 2) { </del> <ins> if (this.numMenusShown - 1 <= showableMenus.length / 4) { </ins> for (const menuBarMenu of showableMenus) { menuBarMenu.buttonElement.style.visibility = 'hidden'; }