When text in Writer and cells in Calc are selected it makes no sense that options Anchor, Arrange, Flip, Group and Graphic in the Format menu are active. Therefore they should be disabled (greyed out) Only when a Graphic object is selected these options should be available. Currently the menu options are available but the submenu options are disabled.. See https://bugs.freedesktop.org/show_bug.cgi?id=42807
for me not reproducible with LO 4.3.2.2 (Win 8.1) Does this issue still persist for you or anybody else with the latest release of LO? Otherwise, we could maybe close this issue as resolved.
(In reply to comment #1) > for me not reproducible with LO 4.3.2.2 (Win 8.1) I don't have 4.3.2 yet but I can reproduce it in 4.3.1.2 > Does this issue still persist for you or anybody else with the latest > release of LO? Otherwise, we could maybe close this issue as resolved. The issue persists in 4.3.1.2
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Over to UX-advise to review. Issue is not limited to selection of Graphic objects as noted by OP, rather it is with the default contextual state of the Split buttons placed on the top level menus. Believe UI/UX question should be: "Should Split buttons on menus be context aware to the context of their child buttons?" With current LibreOffice master, in the UI Split buttons on the menu are active** regardless of contextual applicability of child widgets contained on the menu (buttons, or additional split buttons, etc.). Menu and Split button Behavior is consistent across the UI. If pursued, it would need to be implemented for all Split buttons. IMHO see no substantive reason to refactor--especially piecemeal. Would move to resolve wontfix. =--= ** behavior of the Edit -> Object Split button (controlling OLE elements) seems an anomaly as implemented.
(In reply to V Stuart Foote from comment #4) > Issue is not limited to selection of Graphic objects as noted by OP, rather > it is with the default contextual state of the Split buttons placed on the > top level menus. > > Believe UI/UX question should be: "Should Split buttons on menus be context > aware to the context of their child buttons?" Good point. In fact this also happens for "Split buttons" in Microsoft software so probably this is a limitation. > Would move to resolve wontfix. I agree. Feel free to close it.
Migrating Whiteboard tags to Keywords: (needsDevEval)
We're replacing our use of the 'ux-advise' component with a keyword: Component -> LibreOffice Add Keyword: needsUXEval [NinjaEdit]
It's common good practice to let the user know what's disabled in hierarchies such as page/tab controls or in menus. So the answer to "Should Split buttons on menus be context aware to the context of their child buttons?" is yes - the default function can be disabled - and no in case of 'menu buttons' that do not have a default action but always pop-up a menu that may contain only disabled items. => WF