Description: When I save a custom menu to a file in LO (tested in LO 6.3.1) and later open that file in another LO version (or AOO), some of the default menus are not fully displayed. As an example I add a screenshot of the file in LO 6.0.3. The display errors in older versions of LO and in versions of AOO (even current ones) are much bigger. Steps to Reproduce: 1. create a new text file 2. add a custom menu to the file 3. save the file in the ODF 4. open the file in another (older) version of LO or in AOO Actual Results: Standard menus are no longer fully displayed when such files are opened. Expected Results: Standard menus should be displayed correctly in any program version. Reproducible: Always User Profile Reset: Yes Additional Info: I think the bug affects all program versions 6.x
Created attachment 156185 [details] Incorrect display in LO 6.0.3 when opening the file with user-defined menu
Created attachment 156186 [details] Test file with user-defined menu to reproduce the error
in LO > 6.3.1 it works fine
I see the entry "More breaks >" with Version: 6.2.8.2 Build ID: 6.2.8-3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kde5; Locale: de-DE (en_US.UTF-8); UI-Language: en-US Calc: threaded
> in LO > 6.3.1 it works fine What exactly do you mean? I can also open the sample file in LO 6.3.1 without errors in the menu display. That wasn't part of my bug report either.
Clarification / Supplement: --------------------------- I haven't examined it in detail, but it seems to be that errors always occur when the default menu items of the LO version where a file with custom menu items is created differ from the LO version where the file is opened later. Example: If I create a file with a custom menu in LO 6.3.1 and then open it in LO 6.2.5, there will be no errors in the Insert menu because the Insert default menus in 6.3.1 and 6.2.5 are the same. I note: Incorrect display only occurs if the default menus differ in the participating LO versions.
Maybe let's add this as a UX topic: should we strive to retain backwards compatibility in menu changes? Currently the menu definition XML files have no concept of partial updates. It is all or nothing. This means that it is impossible to use user-defined menus in an older version with an outdated general menu structure. It seems to me that such partial updates might require a rather big effort to achieve.
(In reply to Buovjaga from comment #7) > It seems to me that such partial updates might > require a rather big effort to achieve. No idea how user-defined menus are integrated into the shipped configuration. I believe users can expect a consistency, so if the effort is too large we could show a warning. Maxim, what do you think?
(In reply to Heiko Tietze from comment #8) > No idea how user-defined menus are integrated into the shipped > configuration. Same way this is done for customization which stored in the user profile: There's a menubar.xml file inside the odf package, which overrides the shipped one. So basically this is the same problem as reported for the user profile in Bug 57466. My take is that regardless of the outcome of Bug 57466, user who need to add/remove menu items in a portable way, should really consider creating an extension, instead of this menubar-inside-document misfeature. Extensions have a proper way to merge individual command into the shipped menu structure. In addition, it's possible to change the runtime menu structure using the UNO api, which can be done also from document macros.
Dear joesch04, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug