https://bugs.documentfoundation.org/show_bug.cgi?id=171323
--- Comment #9 from Eyal Rozenberg <[email protected]> --- Bottom line: I say let's drop 'Close' from the File menubutton menu on the side. Why? Because those menus are not full menus anyway, and we already have this function in other places, as Tanuki pointed out. (In reply to V Stuart Foote from comment #8) > Users are already able to customize and remove two of the three. But isn't the possibility of customizing the notebookbar going away to facilitate Heiko's sectioning implementation? (In reply to tanuki.ej9mr from comment #0) Why consider a single command? There is lots and lots of redundancy between menu and notebookbar-button commands, is there not? And indeed, I notice you said this: > I was unable to see a difference presented in the options in the tab "File" > and in the dropdown "File". Therefor I think it would make sense to replace > the tab "File" with a dropdown. This would not only remove a lot of > duplicate options but would also make the layout similar to alternative word > processors. So, are we talking about closing the current file? Or removing dupes from edge-of-notebookbar menusbuttons? Or removing these altogether? Please clarify. > For the exact same reason I would also create a tab called > "Help" which would also act as a dropdown. That would be a separate bug (which already exists IIANM?) > This should in theory make the UI "cleaner" and if implemented correctly > make LibreOffice more intuitive to use. If you want a clean intuitive UI, don't use the notebookbar, use Menus+Toolbars. or Menus + Single Toolbar... > Additional Info: > Version: 24.2.7.2 (X86_64) / LibreOffice Community > Build ID: 420(Build:2) > CPU threads: 16; OS: Linux 6.6; UI render: default; VCL: gtk3 > Locale: en-US (C.UTF-8); UI: en-US > Ubuntu package version: 4:24.2.7-0ubuntu0.24.04.4 While it's not forbidden to file bus using older versions, it's usually a good idea to use the current release version or the latest nightly when filing - to make sure the issue hasn't been resolved already. -- You are receiving this mail because: You are the assignee for the bug.
